| 2.1 |
Approval of the agenda |
|
| R2-2100000 |
Agenda for RAN2#113-e |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2100001 |
RAN2#112-e Meeting Report |
MCC |
| R2-2102242 |
RAN2#111-e Meeting Report |
MCC |
| 2.4 |
Others |
|
| R2-2100351 |
3GPP TSG RAN WG2 Handbook (01/2021) |
ETSI MCC |
| R2-2100352 |
RAN2#113-e Meeting Guidelines |
ETSI MCC |
| R2-2102218 |
Correction of DL End Markers and QoS Flow Mobility |
R3 (Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Deutsche Telekom, CATT) |
| R2-2102219 |
Correction of DL End Markers and QoS Flow Mobility |
R3 (Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Deutsche Telekom, CATT) |
| R2-2102220 |
PDCP SN issue for EPC to 5GC handover |
R3 (Huawei, CATT) |
| 3 |
Incoming liaisons |
|
| R2-2100004 |
Withdrawal of IEEE Std 802.1D-2004 (liaison-8021D-withdrawal-1120-v01; contact: Ericsson) |
IEEE 802.1 |
| R2-2100074 |
LS on Physical layer assisted lightweight AKA (PL-AKA) protocol for the Internet of things (S3-203492; contact: Ericsson) |
SA3 |
| 4.1 |
NB-IoT corrections Rel-15 and earlier |
|
| R2-2101822 |
Correction on NPRACH resources in SIB2-NB and SIB23-NB |
MediaTek Inc., ZTE |
| R2-2101824 |
Correction on NPRACH resources in SIB2-NB and SIB23-NB |
MediaTek Inc., ZTE |
| R2-2102151 |
offline_[AT113-e][301][NBIOT R15] Correction on NPRACH resources |
Mediatek Inc. |
| R2-2102157 |
Correction on NPRACH resources in SIB2-NB and SIB23-NB |
MediaTek Inc., ZTE |
| R2-2102158 |
Correction on NPRACH resources in SIB2-NB and SIB23-NB |
MediaTek Inc., ZTE |
| 4.2 |
eMTC corrections Rel-15 and earlier |
|
| R2-2101041 |
Correction to the applicability of CRS muting configuration |
Huawei, HiSilicon |
| R2-2101042 |
Correction to the applicability of CRS muting configuration |
Huawei, HiSilicon |
| R2-2102061 |
Offline 401 – Applicability of CRS muting configuration |
Huawei |
| 4.4 |
Positioning corrections Rel-15 and earlier |
|
| R2-2100391 |
corrections on the descriptions of RequestLocationInformation message in TS36.305 |
CATT |
| R2-2100392 |
corrections on the descriptions of RequestLocationInformation message in TS36.305 |
CATT |
| R2-2100393 |
corrections on the descriptions of RequestLocationInformation message in TS36.305 |
CATT |
| R2-2100394 |
corrections on the indication for the not provided assistance data and location information in TS36.305 |
CATT |
| R2-2100395 |
corrections on the indication for the not provided assistance data and location information in TS36.305 |
CATT |
| R2-2100396 |
corrections on the indication for the not provided assistance data and location information in TS36.305 |
CATT |
| R2-2101818 |
Correction to the basic production for positioning AD broadcast-R16 |
Huawei, HiSilicon |
| R2-2101819 |
Correction to the basic production for positioning AD broadcast-R15 |
Huawei, HiSilicon |
| R2-2102303 |
Report of [AT113-e][602][POS] LTE Rel-15 positioning CRs (CATT) |
CATT |
| 4.5 |
Other LTE corrections Rel-15 and earlier |
|
| R2-2100436 |
Minor changes collected by Rapporteur for Rel-15 |
Samsung |
| R2-2100437 |
Minor changes collected by Rapporteur for Rel-16 |
Samsung |
| R2-2100778 |
Discussion on ciphering key discrepancy issue for legacy S1-handover |
NTT DOCOMO INC. |
| R2-2100996 |
Miscellaneous corrections on Aerial functionality |
Samsung |
| R2-2100997 |
Miscellaneous corrections on Aerial functionality |
Samsung |
| R2-2101081 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2101084 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2101410 |
On the lack of PLMN identity check in case of anyCellSelected state related logging |
Ericsson |
| R2-2101411 |
Releasing WLAN-BT configuration upon returning from Inactive |
Ericsson |
| R2-2101412 |
On the lack of PLMN identity check in case of anyCellSelected state related logging |
Ericsson |
| R2-2101413 |
Releasing WLAN-BT configuration upon returning from Inactive |
Ericsson |
| R2-2101443 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101444 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101445 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101658 |
CR on overheatingAssistanceConfig release |
Huawei, HiSilicon |
| R2-2101659 |
CR on overheatingAssistanceConfig release |
Huawei, HiSilicon |
| R2-2101962 |
Summary of [AT113-e][202][LTE] LTE Miscellaneous corrections (RAN2 VC) |
Nokia (RAN2 VC) |
| R2-2101982 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2101983 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2101984 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101993 |
Summary of [AT113-e][203][LTE] LTE RRC editorial corrections (Samsung) |
Samsung |
| R2-2101994 |
Minor changes collected by Rapporteur for Rel-15 |
Samsung |
| R2-2101995 |
Minor changes collected by Rapporteur for Rel-16 |
Samsung |
| 5.1 |
Organisational |
|
| R2-2102204 |
Second Reply LS to RP-202935 = R4-2100025 on BCS reporting and support for intra-band EN-DC band combinations (R4-2103401; contact: T-Mobile USA) |
RAN4 |
| R2-2102329 |
Reply LS on the use of simultaneous CSI-RS resources and ports (R1-2101962; contact: Ericsson) |
RAN1 |
| 5.2 |
Stage 2 corrections |
|
| R2-2102268 |
Offline 001 on Stage 2 Corrections |
Nokia (Rapporteur) |
| 5.2.1 |
TS 3x.300 |
|
| R2-2100270 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| R2-2100271 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| R2-2101345 |
Clarification of data forwarding upon intra-system HO using full configuration |
Samsung, Intel Corporation, China Telecom, LGU+, Google Inc., CATT, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R2-2102339 |
Clarification of data forwarding upon intra-system HO using full configuration |
Samsung, Intel Corporation, China Telecom, LGU+, Google Inc., CATT, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R2-2102370 |
Clarification of data forwarding upon intra-system HO using full configuration |
Samsung, Intel Corporation, China Telecom, LGU+, Google Inc., CATT, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| 5.2.2 |
TS 37.340 |
|
| R2-2100091 |
Correction on the PDCP Change Indication for 37.340 |
CATT |
| R2-2100092 |
Correction on the PDCP Change Indication for 37.340 |
CATT |
| R2-2101478 |
Corrections on UL power sharing |
Huawei, HiSilicon, ZTE Corpoation (rapporteur) |
| R2-2101653 |
Correction on user plane handling for full configuration in SN Change |
Google Inc., Samsung, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Motorola Mobility, Intel Corporation |
| R2-2102297 |
Corrections on UL power sharing |
Huawei, HiSilicon, ZTE Corporation (rapporteur) |
| R2-2102366 |
Correction on user plane handling for full configuration in SN Change |
Google, Samsung, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Motorola Mobility, Intel Corporation |
| R2-2102371 |
Correction on user plane handling for full configuration in SN Change |
Google, Samsung, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Motorola Mobility, Intel Corporation |
| 5.3.1 |
MAC |
|
| R2-2100206 |
Miscellaneous corrections |
Samsung |
| R2-2100207 |
Miscellaneous corrections |
Samsung |
| R2-2100315 |
Correction to MAC timer procedures |
Qualcomm Incorporated |
| R2-2100316 |
UE capability for not starting MAC timers |
Qualcomm Incorporated |
| R2-2100317 |
Configuration and capability signaling for not starting MAC timers |
Qualcomm Incorporated |
| R2-2101337 |
Activation of CG and DRX Inactivity Timer |
Ericsson |
| R2-2101344 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2101349 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2101351 |
Activation of CG/SPS and DRX Inactivity Timer |
Apple |
| R2-2101446 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101447 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2101510 |
Activation of CG and DRX Inactivity Timer |
LG Electronics Inc. |
| R2-2101522 |
CR on CG type 1 resources handling when timeAlignmentTimer is expired-Opt 1 |
ZTE Corporation, Sanechips |
| R2-2101523 |
CR on CG type 1 resources handling when timeAlignmentTimer is expired-Opt 2 |
ZTE Corporation, Sanechips |
| R2-2101524 |
CR on CG type 1 resources handling when timeAlignmentTimer is expired-Opt 1 |
ZTE Corporation, Sanechips |
| R2-2101525 |
CR on CG type 1 resources handling when timeAlignmentTimer is expired-Opt 2 |
ZTE Corporation, Sanechips |
| R2-2101593 |
Discussion on the handling of CG type 1 resources when TA timer is expired |
ZTE Corporation, Sanechips |
| R2-2101769 |
Further discussions on DRX InactivityTimer operations |
Huawei, HiSilicon |
| R2-2101770 |
Discussion on UE behaviors for MAC reset |
Huawei, HiSilicon |
| R2-2101771 |
Correction to TS 38.321 on MAC Reset |
Huawei, HiSilicon |
| R2-2101772 |
Correction to TS 38.321 on MAC Reset |
Huawei, HiSilicon |
| R2-2101773 |
Correction on CSI reporting when CSI masking is setup |
Huawei, HiSilicon |
| R2-2101774 |
Correction on CSI reporting when CSI masking is setup |
Huawei, HiSilicon |
| R2-2102283 |
Correction on CSI reporting when CSI masking is setup |
Huawei, HiSilicon |
| R2-2102284 |
Correction on CSI reporting when CSI masking is setup |
Huawei, HiSilicon |
| R2-2102290 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2102291 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2102320 |
Report of [AT113-e][002][NR15] User Plane I (Samsung) |
Samsung |
| R2-2102321 |
Miscellaneous corrections |
Samsung, Qualcomm |
| R2-2102322 |
Miscellaneous corrections |
Samsung, Qualcomm |
| R2-2102323 |
Activation of CG and DRX inactivity timer |
Samsung |
| R2-2102337 |
Activation of CG and DRX inactivity timer |
Samsung |
| R2-2102395 |
Report of [AT113-e][003][NR15] User Plane II (Huawei) |
Huawei |
| R2-2102396 |
Corrections to MAC reset |
Huawei, HiSilicon, Ericsson |
| R2-2102437 |
Corrections to MAC reset |
Ericsson, Huawei |
| R2-2102506 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2102507 |
Clarification to LCP restrictions |
Ericsson, Mediatek |
| R2-2102517 |
Correction on CSI reporting when CSI masking is setup |
Huawei, HiSilicon |
| R2-2102519 |
Corrections to MAC reset |
Huawei, HiSilicon, Ericsson |
| 5.3.2 |
RLC |
|
| R2-2101441 |
Clarification to RLC PDU Polling at Handover |
Ericsson |
| R2-2101442 |
Clarification to RLC PDU Polling at Handover |
Ericsson |
| 5.3.3 |
PDCP |
|
| R2-2101775 |
Discussion about RoHC handling during PDCP re-establishment |
Huawei, HiSilicon |
| 5.4.1.1 |
Connection control |
|
| R2-2100057 |
LS on RRC based BWP switch for Scell (R4-2017040; contact: Apple) |
RAN4 |
| R2-2100369 |
PDCP re-establishment for SRB1 after RRC Reestablishment |
Intel Corporation, Ericsson |
| R2-2100551 |
Report of Email discussion[061][NR15] Configuration of First Active BWP |
ZTE Corporation, Sanechips |
| R2-2100552 |
CR on SyncAndCellAdd condition |
ZTE Corporation, Sanechips, Huawei, HiSilicon |
| R2-2100553 |
CR on SyncAndCellAdd condition |
ZTE Corporation, Sanechips, Huawei, HiSilicon |
| R2-2100554 |
Further discussion on scrambling ID fields |
ZTE Corporation, Sanechips, CATT |
| R2-2100555 |
CR to clarify UE behaivour for scrambling ID fields |
ZTE Corporation, Sanechips, CATT |
| R2-2100556 |
CR to clarify UE behaivour for scrambling ID fields |
ZTE Corporation, Sanechips, CATT |
| R2-2100557 |
Clarification on procedure of DRB release |
ZTE Corporation, Sanechips |
| R2-2100558 |
CR to clarify the procedure of DRB release |
ZTE Corporation, Sanechips |
| R2-2100559 |
CR to clarify the procedure of DRB release |
ZTE Corporation, Sanechips |
| R2-2100756 |
RLC Mode Restrictions |
Nokia, Ericsson (Rapporteur), Nokia Shanghai Bell |
| R2-2100757 |
RLC Mode Restrictions |
Nokia, Ericsson (Rapporteur), Nokia Shanghai Bell |
| R2-2100765 |
Clarification on P-max in FrequencyInfoUL in FR2 |
NTT DOCOMO, INC. |
| R2-2100771 |
Clarification on P-max in FrequencyInfoUL in FR2 |
NTT DOCOMO, INC. |
| R2-2100841 |
Further Clarification on RRC Local Release |
vivo |
| R2-2100945 |
Clarification on RRC based BWP switch for SCell |
Nokia, Nokia Shanghai Bell |
| R2-2100969 |
Clarification on SRB1 configuration for RRC resume |
Ericsson, Intel, ZTE Corporation, Sanechips |
| R2-2101019 |
RRC-based BWP switch for SpCell and SCells |
vivo |
| R2-2101166 |
Discussion on RRC based BWP switch for Pcell |
ZTE Corporation, Sanechips |
| R2-2101167 |
Discussion on RRC based BWP switch for SCell based on RAN4 LS(R4-2017040) |
ZTE Corporation, Sanechips |
| R2-2101267 |
Clarification of Note for leaving source cell at reconfigurationWithSync |
Ericsson |
| R2-2101268 |
Clarification of Note for leaving source cell at reconfigurationWithSync |
Ericsson |
| R2-2101459 |
[Draft] LS Reply on RRC based BWP switch |
Apple Inc |
| R2-2101462 |
Discussion on RRC-based BWP switch |
Apple Inc |
| R2-2101732 |
p-Max for FR2 in dedicated signalling |
Ericsson |
| R2-2102293 |
Summary of [AT113-e][005][NR15] Connection Control II (Apple) |
Apple Inc |
| R2-2102365 |
Report: [AT113-e][004][NR15] Connection Control I (ZTE) |
ZTE Corporation (email rapporteur) |
| R2-2102476 |
LS Reply on RRC based BWP switch |
RAN2 |
| 5.4.1.2 |
RRM and Measurements and Measurement Coordination |
|
| R2-2100063 |
LS on reporting of SINR measurements for serving cell (R5-206274; contact: Qualcomm) |
RAN5 |
| R2-2101422 |
On trigger quantity related clarification |
Ericsson |
| R2-2101423 |
On trigger quantity related clarification |
Ericsson |
| R2-2101834 |
Discussion on reporting of SINR measurements for serving cell |
MediaTek Inc. |
| R2-2102285 |
Report of [Offline-006][NR15] Measurements Misc and System Info |
Ericsson |
| R2-2102312 |
Reply LS on reporting of SINR measurements for serving cell |
RAN2 |
| R2-2102499 |
Reply LS on reporting of SINR measurements for serving cell |
RAN2 |
| 5.4.1.3 |
System information |
|
| R2-2100751 |
The validity of a stored SIB if SI Area ID is absent |
Fujitsu |
| 5.4.1.4 |
Inter-Node RRC messages |
|
| R2-2100586 |
Clarification on inter node signalling upon SN initiated SCG release |
Samsung Telecommunications |
| R2-2100772 |
Clarification on band combination selection over inter-node message |
NTT DOCOMO INC. |
| R2-2100773 |
Clarification on band combination selection over inter-node message |
NTT DOCOMO INC. |
| R2-2101021 |
Companion paper for CR proposed for intra-band EN-DC deployment issue |
Nokia, Nokia Shanghai Bell |
| R2-2101022 |
Inter-node messaging for supporting intra-band EN-DC scenarios |
Nokia, Nokia Shanghai Bell |
| R2-2101347 |
Discussion on inter-node coordination of message size in MR-DC |
Samsung Telecommunications |
| R2-2101705 |
Discusson on the usage of MN and SN configuration restrictions |
Huawei, HiSilicon |
| R2-2101931 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2101932 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2101934 |
Clarification on band combination selection over inter-node RRC message |
NTT DOCOMO INC. |
| R2-2101935 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2101936 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2101944 |
Lack of late non-critical extensions in inter-node messages |
Nokia, Nokia Shanghai Bell |
| R2-2102360 |
[Draft] Reply LS on signalling SN initiated release of SCG |
Samsung |
| R2-2102440 |
Clarification to usage of ConfigRestrictModReqSCG |
Nokia, Nokia Shanghai Bell |
| R2-2102441 |
Clarification to usage of ConfigRestrictModReqSCG |
Nokia, Nokia Shanghai Bell |
| R2-2102442 |
Inter-node messaging for supporting intra-band EN-DC scenarios |
Nokia, Nokia Shanghai Bell |
| R2-2102443 |
Summary of [AT113-e][007][NR15] Inter Node RRC (Nokia) |
Nokia |
| R2-2102456 |
Clarification on band combination selection over inter-node message |
NTT DOCOMO INC. |
| R2-2102457 |
Clarification on band combination selection over inter-node RRC message |
NTT DOCOMO INC. |
| R2-2102486 |
[Draft] Reply LS on signalling SN initiated release of SCG |
Samsung |
| R2-2102493 |
LS on signalling SN initiated release of SCG |
RAN2 |
| R2-2102496 |
Inter-node messaging for supporting intra-band EN-DC scenarios |
Nokia, Nokia Shanghai Bell |
| 5.4.1.5 |
Other |
|
| R2-2101285 |
Miscellaneous non-controversial corrections Set IX |
Ericsson |
| R2-2102380 |
Miscellaneous non-controversial corrections Set IX |
Ericsson |
| 5.4.2 |
LTE changes related to NR |
|
| R2-2100182 |
A remaining issue in SIB extension |
Samsung Electronics Co., Ltd |
| R2-2100946 |
Handling of 4-layer MIMO in EN-DC for Cat5 UEs |
Nokia, Nokia Shanghai Bell |
| R2-2101863 |
Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously |
Qualcomm Incorporated |
| R2-2101864 |
Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously |
Qualcomm Incorporated |
| R2-2101881 |
Correction on IDC indication |
Samsung |
| R2-2101882 |
Correction on IDC indication |
Samsung |
| R2-2102444 |
Summary of [AT113-e][008][NR15] LTE changes (Nokia) |
Nokia |
| 5.4.3 |
UE capabilities and Capability Coordination |
|
| R2-2100016 |
Reply LS on UE capability xDD differentiation for SUL/SDL bands (R1-2009576; contact: Samsung) |
RAN1 |
| R2-2100020 |
LS on Interpretation of UE Features in Case of Cross-Carrier Operation (R1-2009623; contact: ZTE) |
RAN1 |
| R2-2100056 |
LS on simultaneous Rx/Tx capability (R4-2016988; contact: Huawei) |
RAN4 |
| R2-2100064 |
LS on single UL operation (RP-202932; contact: Huawei) |
RAN |
| R2-2100065 |
LS on BCS reporting and support for intra-band EN-DC band combinations (RP-202935; contact: Nokia) |
RAN |
| R2-2100388 |
Clarification on BCS reporting and support for intra-band EN-DC band combinations |
Intel Corporation |
| R2-2100439 |
xDD differentiation of UE capabilities for SUL/SDL bands |
Samsung |
| R2-2100440 |
xDD differentiation of UE capabilities for SUL/SDL bands |
Samsung |
| R2-2100481 |
BCS reporting for intra-band EN-DC band combination |
Qualcomm Incorporated |
| R2-2100947 |
Handling of single UL for intra-band EN-DC band combinations |
Nokia, Nokia Shanghai Bell |
| R2-2100948 |
Handling of single UL for intra-band EN-DC band combinations |
Nokia, Nokia Shanghai Bell |
| R2-2100949 |
Clarifying BCS for inter-band EN-DC band combination with intra-band EN-DC components |
Nokia, Nokia Shanghai Bell |
| R2-2100961 |
Handling of single UL for intra-band EN-DC band combinations |
Nokia, Nokia Shanghai Bell |
| R2-2100962 |
Handling of single UL for intra-band EN-DC band combinations |
Nokia, Nokia Shanghai Bell |
| R2-2100970 |
Dummy the capability bit v2x-EUTRA |
Ericsson |
| R2-2100971 |
Dummy the capability bit v2x-EUTRA |
Ericsson |
| R2-2100972 |
Dummy the capability bit v2x-EUTRA |
Ericsson |
| R2-2101354 |
Clarification on the capability of supportedNumberTAG |
Apple |
| R2-2101430 |
Definition of Fallback per CC feature set |
Ericsson |
| R2-2101431 |
Definition of fallback per CC feature set |
Ericsson |
| R2-2101432 |
Per UE capability differentiation for SUL bands |
Ericsson |
| R2-2101435 |
On the use of UE simultaneous Rx/Tx capability |
Ericsson |
| R2-2101558 |
Clarification on the BWP Configuration Capabilities |
ZTE Corporation, Sanechips |
| R2-2101559 |
CR on the SupportedBandwidth/channelBWs-R15 |
ZTE Corporation, Sanechips |
| R2-2101560 |
CR on the SupportedBandwidth/channelBWs-R16 |
ZTE Corporation, Sanechips |
| R2-2101561 |
Clarification on the SingleUL-Transmission |
ZTE Corporation, Sanechips |
| R2-2101562 |
Clarification on the Intra-band and Inter-band EN-DC Capabilities |
ZTE Corporation, Sanechips |
| R2-2101563 |
CR on the Intra-band and Inter-band EN-DC Capabilities - R15 |
ZTE Corporation, Sanechips |
| R2-2101564 |
CR on the Intra-band and Inter-band EN-DC Capabilities - R16 |
ZTE Corporation, Sanechips |
| R2-2101565 |
Draft LS on the Intra-band and Inter-band EN-DC Capabilities |
ZTE Corporation, Sanechips |
| R2-2101660 |
Discussion on the definition of fallback per CC feature set |
Huawei, HiSilicon |
| R2-2101661 |
CR to clarify the definition of fallback per CC feature set |
Huawei, HiSilicon |
| R2-2101662 |
Discussion on simultaneous RxTx capability (LS contact) |
Huawei, HiSilicon |
| R2-2101663 |
Draft reply LS on simultaneous RxTx capability |
Huawei, HiSilicon |
| R2-2101664 |
Discussion on BCS for intra-band EN-DC BC with inter-band component |
Huawei, HiSilicon |
| R2-2101731 |
DL scheduling slot offset capability |
Ericsson, Qualcomm |
| R2-2101843 |
Discussion on simultaneous Rx/Tx capability |
MediaTek Inc. |
| R2-2101844 |
Clarification on the simultaneousRxTxInterBandCA capability in NR-DC |
MediaTek Inc. |
| R2-2101845 |
Clarification on the simultaneousRxTxInterBandCA capability in NR-DC |
MediaTek Inc. |
| R2-2101911 |
Clarification on FDD-TDD differentiation for SUL band |
Huawei, HiSilicon, Intel Corporation |
| R2-2101912 |
Clarification on FDD-TDD differentiation for SUL band |
Huawei, HiSilicon |
| R2-2101913 |
Clarification on single uplink operation capability report |
Huawei, HiSilicon |
| R2-2101914 |
Clarification on single uplink operation capability report |
Huawei, HiSilicon |
| R2-2102166 |
Summary of [Post113-e][009][NR15] EN-DC BCS (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2102167 |
Clarification on the supportedBandwidthCombinationSetIntraENDC capability |
Nokia, Nokia Shanghai Bell |
| R2-2102168 |
Clarification on the supportedBandwidthCombinationSetIntraENDC capability |
Nokia, Nokia Shanghai Bell |
| R2-2102215 |
Summary of [Post113-e][009][NR15] EN-DC BCS (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2102216 |
Clarification on the supportedBandwidthCombinationSetIntraENDC capability |
Nokia, Nokia Shanghai Bell |
| R2-2102217 |
Clarification on the supportedBandwidthCombinationSetIntraENDC capability |
Nokia, Nokia Shanghai Bell |
| R2-2102372 |
Summary of [011][NR15] UE Capabilites III (Samsung) |
Samsung |
| R2-2102374 |
Summary of [012][NR15] UE Capabilites IV (Huawei |
Huawei, HiSilicon |
| R2-2102376 |
CR to clarify the definition of fallback per CC feature set |
Huawei, HiSilicon |
| R2-2102377 |
CR to clarify the definition of fallback per CC feature set |
Huawei, HiSilicon |
| R2-2102379 |
Draft reply LS on simultaneous RxTx capability |
Huawei, HiSilicon |
| R2-2102389 |
Clarification on FDD-TDD differentiation for SUL band |
Huawei, HiSilicon, Intel Corporation, Ericsson |
| R2-2102390 |
Clarification on FDD-TDD differentiation for SUL band |
Huawei, HiSilicon, Ericsson |
| R2-2102391 |
Clarification on single uplink operation capability report |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2102392 |
Clarification on single uplink operation capability report |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2102400 |
Summary of offline [AT113-e][010][NR15] UE Capabilities II (ZTE) |
ZTE, Sanechips |
| R2-2102401 |
CR on the SupportedBandwidth and channelBWs(R15) |
ZTE Corporation, Sanechips |
| R2-2102402 |
CR on the SupportedBandwidth and channelBWs(R16) |
ZTE Corporation, Sanechips |
| R2-2102403 |
Reply LS to RP-202935 on BCS reporting and support for intra-band EN-DC band combinations (R4-2102149; contact: T-Mobile USA) |
RAN4 |
| R2-2102445 |
Summary of [AT113-e][009][NR15] UE Capabilites EN-DC BCS (Nokia) |
Nokia |
| R2-2102466 |
Dummy the capability bit v2x-EUTRA |
Ericsson |
| R2-2102467 |
Dummy the capability bit v2x-EUTRA |
Ericsson |
| R2-2102473 |
Clarification on the capability of supportedNumberTAG |
Apple |
| R2-2102481 |
Clarification on the capability of supportedNumberTAG |
Apple, Nokia |
| R2-2102490 |
Clarification on the capability of supportedNumberTAG |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2102491 |
Clarification on the capability of supportedNumberTAG |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2102495 |
Reply LS on simultaneous RxTx capability |
RAN2 |
| R2-2102510 |
CR on the SupportedBandwidth and channelBWs(R15) |
ZTE Corporation, Sanechips |
| R2-2102511 |
CR on the SupportedBandwidth and channelBWs(R16) |
ZTE Corporation, Sanechips |
| R2-2102518 |
Clarification on FDD-TDD differentiation for SUL band |
Huawei, HiSilicon, Ericsson |
| 5.4.4 |
Idle/inactive mode procedures |
|
| R2-2100181 |
Way forward for open issue on mobility state determination |
Samsung Electronics Co., Ltd |
| R2-2100247 |
Corrections for Inactive |
OPPO |
| R2-2100248 |
Corrections for Inactive |
OPPO |
| R2-2100306 |
Clarification on UE power class in S Criterion-R15 |
OPPO |
| R2-2100307 |
Clarification on UE power class in S Criterion-R16 |
OPPO |
| R2-2101249 |
Discussion on Inter-RAT Cell Reselection and Mobility State |
Huawei, HiSilicon |
| R2-2101250 |
Correction to Inter-RAT Cell Reselection and Mobility State |
Huawei, HiSilicon |
| R2-2101355 |
Clarification on Inter-RAT Cell Reselection and Mobility State |
Apple |
| R2-2101840 |
Discussion on Inter-RAT Cell Reselection and Mobility State |
MediaTek Inc. |
| R2-2101896 |
Clarification of inter-RAT Cell Reselection for Mobility State Determination |
Qualcomm Incorporated |
| R2-2101897 |
Clarification of inter-RAT Cell Reselection for Mobility State Determination |
Qualcomm Incorporated |
| R2-2102310 |
Report of [AT113-e][013][NR15] Idle Inactive (Mediatek) |
MediaTek |
| R2-2102311 |
LS on inter-RAT cell reselection for mobility state estimation |
RAN2 |
| 5.5 |
Positioning corrections |
|
| R2-2100397 |
Remove the NOTE in architecture figure in TS38.305 |
CATT |
| R2-2100398 |
corrections on the indication for the not provided assistance data and location information in TS38.305 |
CATT |
| R2-2100399 |
corrections on the indication for the not provided assistance data and location information in TS38.305 |
CATT |
| R2-2100400 |
corrections on the descriptions of RequestLocationInformation message in TS38.305 |
CATT |
| R2-2100401 |
corrections on the descriptions of RequestLocationInformation message in TS38.305 |
CATT |
| R2-2101379 |
GNSS RTK observations resolution indication |
Ericsson |
| R2-2101380 |
Correction of A-GNSS Assistance Data RTK Observation |
Ericsson |
| R2-2101381 |
Correction of A-GNSS Assistance Data RTK Observation |
Ericsson |
| R2-2101465 |
Support OTDOA assistance data for case of NR serving cell |
Qualcomm Incorporated, Ericsson |
| R2-2101468 |
Support OTDOA assistance data for case of NR serving cell |
Qualcomm Incorporated, Ericsson |
| R2-2101815 |
Clarification on E-CID and NR E-CID |
Huawei, HiSilicon |
| R2-2101816 |
Correction to E-CID-R15 |
Huawei, HiSilicon |
| R2-2101817 |
Correction to E-CID-R16 |
Huawei, HiSilicon |
| R2-2101926 |
Correction on the descritpion for UE capability transfer-R15 |
Huawei, HiSilicon |
| R2-2101927 |
Correction on the descritpion for UE capability transfer-R16 |
Huawei, HiSilicon |
| R2-2101928 |
Correction to 5G support for NB-IOT positioning-R15 |
Huawei, HiSilicon |
| R2-2101929 |
Correction to 5G support for NB-IOT positioning-R16 |
Huawei, HiSilicon |
| R2-2102102 |
Summary of Email discussion [AT113-e][603][POS] NR Rel-15 positioning CRs |
Qualcomm Incorporated |
| R2-2102104 |
[DRAFT] LS on E-CID LTE measurement in Rel-15 |
Huawei |
| R2-2102128 |
LS on E-CID LTE measurement in Rel-15 |
RAN2 |
| R2-2102516 |
Support OTDOA assistance data for case of NR serving cell |
Qualcomm Incorporated, Ericsson |
| 6.1.1 |
General RRC corrections |
|
| R2-2100101 |
Co-configuration of V2X and other features |
OPPO |
| R2-2100102 |
CR on co-configuration of NR-V2X and other features |
OPPO |
| R2-2100103 |
CR on Co-configuration of NR-V2X and MR-DC |
OPPO |
| R2-2100104 |
CR on co-configuration of CHO and UAI and SUI report |
OPPO |
| R2-2100149 |
DAPS HO and NR Sidelink Communication |
Samsung Electronics Co., Ltd |
| R2-2100302 |
Clarficiations on the required SIB or posSIB |
CATT |
| R2-2100526 |
Transmitting SL UE Information after CHO |
Nokia, Nokia Shanghai Bell |
| R2-2100680 |
UE information transmission in NR CHO case |
SHARP Corporation, Ericsson |
| R2-2100681 |
UE information transmission in LTE CHO case |
SHARP Corporation, Ericsson |
| R2-2100887 |
Co-configuration of NR-IIoT and other features |
OPPO |
| R2-2100888 |
CR on co-configuration of NR-IIoT and other features |
OPPO |
| R2-2100973 |
Coexistance of DAPS and Sidelink |
Ericsson |
| R2-2100974 |
Correction to measResultServingMOList impacting EN-DC |
Ericsson |
| R2-2100975 |
Correction to measResultPCell impacting EN-DC |
Ericsson |
| R2-2101023 |
Introducing UE Config Release for NR |
Nokia, Nokia Shanghai Bell |
| R2-2101024 |
Improving description of ue-ConfigRelease |
Nokia, Nokia Shanghai Bell |
| R2-2101169 |
Retransmission of UE information after CHO |
Google Inc. |
| R2-2101182 |
Retransmission of UE information after CHO |
Google Inc. |
| R2-2101286 |
Miscellaneous non-controversial corrections Set IX |
Ericsson |
| R2-2101324 |
Correction on releasing referenceTimePreferenceReporting and other fields |
Huawei, HiSilicon |
| R2-2101474 |
Summary of email discussion [Post112-e][060][NR16] Extension of ToAddMod lists (MediaTek) |
MediaTek Inc. |
| R2-2101475 |
ASN.1 guidelines for extension of lists using ToAddMod structure |
MediaTek Inc. |
| R2-2101535 |
CR on measurement object modification |
ZTE Corporation, Sanechips |
| R2-2101546 |
Clarification on ULInformationTransferMRDC message |
ZTE Corporation, Sanechips |
| R2-2101571 |
Corrections to on-demand SI |
ZTE Corporation, Sanechips |
| R2-2101687 |
Correnctions on the default configuration with Need M |
Huawei, HiSilicon |
| R2-2101702 |
Clarification on DAPS HO configuration |
vivo |
| R2-2101733 |
Clarification for SIBs scheduled in posSchedulingInfoList |
Ericsson |
| R2-2101825 |
Correction to the UE action upon SIB1 reception |
Huawei, HiSilicon, Ericsson |
| R2-2102256 |
ASN.1 guidelines for extension of lists using ToAddMod structure |
MediaTek Inc. |
| R2-2102292 |
ASN.1 guidelines for extension of lists using ToAddMod structure |
MediaTek Inc. |
| R2-2102294 |
Summary of [AT113-e][016][POS V2X NR16] RRC III |
Ericsson |
| R2-2102298 |
Correnctions on the default configuration with Need M |
Huawei, HiSilicon |
| R2-2102324 |
Corrections to on-demand SI |
ZTE Corporation, Sanechips |
| R2-2102381 |
Miscellaneous non-controversial corrections Set IX |
Ericsson |
| R2-2102386 |
Email discussion report [AT113-e][014][NR16] RRC I (Ericsson) |
Ericsson |
| R2-2102404 |
Clarification for SIBs scheduled in posSchedulingInfoList |
Ericsson |
| R2-2102406 |
Clarification on DAPS HO configuration |
vivo |
| R2-2102410 |
Summary of [AT113-e][015][NR16 V2X MOB DCCA] RRC II (OPPO) |
OPPO |
| R2-2102411 |
CR on co-configuration of Rel-16 features |
OPPO |
| R2-2102412 |
CR on co-configuration of sidelink and MR-DC |
OPPO |
| R2-2102415 |
CR on measurement object modification |
ZTE Corporation, Sanechips |
| R2-2102416 |
Clarification on ULInformationTransferMRDC message |
ZTE Corporation, Sanechips |
| R2-2102448 |
Clarification on DAPS HO configuration |
vivo |
| R2-2102450 |
Corrections on the default configuration with Need M |
Huawei, HiSilicon |
| R2-2102468 |
Clarficiations on the required posSIB |
CATT |
| 6.1.2 |
NR Feature Lists and UE capabilities |
|
| R2-2100008 |
LS on TPMI grouping capability (R1-2009449; contact: vivo) |
RAN1 |
| R2-2100013 |
Reply LS to RAN2 on beamSwitchTiming (R1-2009496; contact: vivo) |
RAN1 |
| R2-2100018 |
LS on updated Rel-16 RAN1 UE features lists for NR (R1-2009586; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2100053 |
LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2016849; contact: CMCC) |
RAN4 |
| R2-2100060 |
LS on Rel-16 mandatory RRM requirements (R4-2017803; contact: CMCC) |
RAN4 |
| R2-2100378 |
Report of [Post112-e][062][NR16] RAN2 Feature List for TR (Intel) |
Intel Corporation |
| R2-2100385 |
UE capability of NR to UTRA-FDD CELL_DCH CS handover |
Intel Corporation |
| R2-2100386 |
UE capability of NR to UTRA-FDD CELL_DCH CS handover |
Intel Corporation |
| R2-2100452 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2100453 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2100454 |
Correction on beamSwitchTiming-r16 capability |
vivo, Intel Corporation |
| R2-2100455 |
Correction on TPMI grouping capability |
vivo, Intel Corporation |
| R2-2100621 |
UE Feature list for NR Rel-16 |
Intel Corporation |
| R2-2100954 |
Capturing suppport of mandatory Rel-16 requirements |
Nokia, Nokia Shanghai Bell |
| R2-2101020 |
Fixing issue with FGs 22-8a/b/c/d |
Nokia, Nokia Shanghai Bell |
| R2-2101058 |
Handling of other TEI features |
Lenovo, Motorola Mobility |
| R2-2101433 |
Clarification on UE capabilities with FDD/TDD differentiation |
Ericsson |
| R2-2101486 |
Correction on UE capabilities for enhanced MIMO |
Huawei, HiSilicon |
| R2-2101821 |
Capability for dormant BWP switching of multiple SCells |
MediaTek Inc. |
| R2-2101873 |
CR on the Capability of PUCCH transmissions for HARQ-ACK-38331 |
ZTE Corporation, Sanechips,Intel |
| R2-2101874 |
CR on the Capability of PUCCH transmissions for HARQ-ACK-38306 |
ZTE Corporation, Sanechips,Intel |
| R2-2101946 |
Configuration for directional collision handling between reference cell and other cell for half-duplex operation in CA |
Nokia Italy |
| R2-2101948 |
Configuration for directional collision handling between reference cell and other cell for half-duplex operation in CA |
Nokia Italy |
| R2-2102129 |
Release-16 UE capabilities based on updated RAN1 and RAN4 feature lists |
Intel Corporation |
| R2-2102130 |
Release-16 UE capabilities based on updated RAN1 and RAN4 feature lists |
Intel Corporation |
| R2-2102263 |
CR on the Capability of PUCCH Transmissions for HARQ-ACK-38331 |
ZTE Corporation, Sanechips,Intel |
| R2-2102264 |
CR on the Capability of PUCCH Transmissions for HARQ-ACK-38306 |
ZTE Corporation, Sanechips,Intel |
| R2-2102296 |
LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2103480; contact: CMCC) |
RAN4 |
| R2-2102325 |
Addition of TEI16 features |
Lenovo, Motorola Mobility |
| R2-2102326 |
[AT113-e][018][NR16] Summary of UE Cap Main (Intel) |
Intel Corporation |
| R2-2102338 |
Reply LS on Rel-16 mandatory RRM requirements |
RAN2 |
| R2-2102407 |
UE capability of NR to UTRA-FDD CELL_DCH CS handover |
Intel Corporation |
| R2-2102408 |
UE capability of NR to UTRA-FDD CELL_DCH CS handover |
Intel Corporation |
| R2-2102409 |
[AT113-e][018][NR16] Summary of UE Cap Main (Intel) |
Intel Corporation |
| R2-2102424 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2102425 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2102426 |
Correction on beamSwitchTiming-r16 capability |
vivo, Intel Corporation |
| R2-2102427 |
Correction on TPMI grouping capability |
vivo, Intel Corporation |
| R2-2102428 |
Capability for dormant BWP switching of multiple SCells |
MediaTek Inc. |
| R2-2102429 |
Capability for dormant BWP switching of multiple SCells |
MediaTek Inc. |
| R2-2102436 |
Clarification on UE capabilities with FDD/TDD differentiation |
Ericsson |
| R2-2102455 |
Clarification on UE capabilities for enhanced MIMO |
Huawei, HiSilicon |
| R2-2102514 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2102515 |
Correction on beamSwitchTiming capability |
vivo, Intel Corporation |
| R2-2102520 |
Clarification on UE capabilities with FDD/TDD differentiation |
Ericsson |
| 6.1.3 |
Other |
|
| R2-2100028 |
LS on PUSCH skipping with UCI in Rel-16 (R1-2009772; contact: vivo) |
RAN1 |
| R2-2100138 |
Remaining Issues on PUSCH Skipping with UCI in Rel-16 |
vivo |
| R2-2100218 |
Correction for DG and CG UL skipping with UCI overlap |
CATT |
| R2-2100314 |
Correction to timeline for determining PH type |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Apple, Ericsson |
| R2-2100340 |
UL PUSCH skipping without intra-UE prioritization |
Ericsson |
| R2-2100341 |
UL PUSCH skipping with Intra-UE prioritization |
Ericsson |
| R2-2100524 |
Draft Reply LS on PUSCH skipping with UCI in Rel-16 |
vivo |
| R2-2100733 |
UE capability for enhanced PHR timeline |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Apple, Ericsson |
| R2-2100734 |
Configuration and capability signaling for enhanced PHR timeline |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Apple, Ericsson |
| R2-2100855 |
UL skipping and intra-UE prioritization |
Apple |
| R2-2101352 |
RAN2 Impact on UL Skipping Enhancement |
Apple |
| R2-2101377 |
MAC CR on UL skipping enhancement |
Apple |
| R2-2101378 |
RRC CR on UL skipping enhancement |
Apple |
| R2-2101456 |
UE capability on UL skipping enhancement |
Apple |
| R2-2101776 |
Updates to RAN2 aspects of PUSCH with UL skipping |
Huawei, HiSilicon |
| R2-2101777 |
Discussion on PHR reporting for PUSCH skipping |
Huawei, HiSilicon |
| R2-2101793 |
Correction on CG-DG skipping capabilities and configuration when PUCCH with UCI overlaps with PUSCH |
CATT |
| R2-2101794 |
Correction on CG and DG skipping capabilities when PUCCH with UCI overlaps with PUSCH |
CATT |
| R2-2102373 |
Report of [AT113-e][020][NR16] MAC PH type (Qualcomm) |
Qualcomm |
| R2-2102458 |
Report of [AT113-e][019][NR16 IIOT] UL Skipping |
vivo |
| R2-2102459 |
Correction to PUSCH skipping with UCI without LCH-based prioritization |
Huawei, HiSilicon, vivo, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, OPPO, CATT |
| R2-2102460 |
Correction to PUSCH skipping with UCI without LCH-based prioritization |
vivo, Samsung |
| R2-2102461 |
Correction on CG and DG skipping capabilities when PUCCH with UCI overlaps with PUSCH |
CATT, vivo |
| R2-2102462 |
Reply LS on PUSCH skipping with UCI in Rel-16 |
RAN2 |
| R2-2102478 |
Correction to PUSCH skipping with UCI without LCH-based prioritization |
CATT, vivo |
| 6.2 |
Integrated Access and Backhaul |
|
| R2-2102314 |
Summary of [AT113-e][021][IAB] RRC and Stage 2 (ZTE) |
ZTE |
| 6.2.1 |
General and Stage-2 Corrections |
|
| R2-2100465 |
Miscellaneous corrections to TS 38.300 for IAB |
vivo |
| R2-2101278 |
Miscellaneous corrections on IAB in 38.300 |
ZTE, Sanechips |
| R2-2101684 |
Corrections for IAB related configurations and procedures on TS 38.300 |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2102315 |
Miscellaneous Stage-2 corrections of IAB in 38.300 |
ZTE, Sanechips, vivo, Huawei |
| 6.2.2 |
BAP Corrections |
|
| R2-2100224 |
Clarify the Buffer Type in Flow Control Feedback |
CATT |
| R2-2100466 |
Correction on the illustration of BAP entity |
vivo |
| R2-2100467 |
Discussion on the modelling of BAP layer |
vivo |
| R2-2101281 |
Miscellaneous corrections on IAB in 38.340 |
ZTE, Sanechips |
| R2-2101452 |
Handling of Unknown and Reserved Values in the BAP Header |
Ericsson |
| R2-2101683 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon (Rapporteur) |
| R2-2102299 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon, vivo, ZTE, Sanechips |
| R2-2102397 |
[Offline-022][IAB] User Plane (vivo) |
vivo |
| R2-2102398 |
Correction on the illustration of BAP entity |
vivo |
| 6.2.3 |
User plane Corrections |
|
| R2-2100468 |
Corrections on the description of Pre-emptive BSR and Guard Symbols MAC CEs |
vivo |
| R2-2102399 |
Corrections on the description of Pre-emptive BSR MAC CE |
vivo |
| 6.2.4 |
RRC Corrections |
|
| R2-2100469 |
Miscellaneous corrections to TS 38.331 for IAB |
vivo |
| R2-2100470 |
Correction on RLC-Config of BH RLC channel |
vivo |
| R2-2101279 |
Correction on AvailabilityCombinationsPerCell IE in 38.331 |
ZTE, Sanechips |
| R2-2101280 |
Miscellaneous corrections on IAB in 38.331 |
ZTE, Sanechips |
| R2-2101685 |
Corrections on BAP address and default BAP configuration |
Huawei, HiSilicon, Ericsson |
| R2-2101686 |
Corrections on the P-max for IAB |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2101904 |
Correction on ULInformationTransfer failure |
Samsung R&D Institute UK |
| R2-2102316 |
Miscellaneous corrections on IAB in 38.331 |
ZTE, Sanechips, vivo, Samsung |
| R2-2102350 |
Miscellaneous corrections on IAB in 38.331 |
ZTE, Sanechips, vivo |
| R2-2102477 |
Corrections on BAP address and default BAP configuration |
Huawei, HiSilicon, Ericsson |
| 6.3.1 |
General and Stage-2 Corrections |
|
| R2-2100006 |
Reply LS on UE capability on wideband carrier operation for NR-U (R1-2009385; contact: MediaTek) |
RAN1 |
| R2-2100228 |
Discussion on differentiation of Rel-16 features for NR operation in shared spectrum |
Huawei, HiSilicon |
| 6.3.2 |
User plane |
|
| R2-2100217 |
Handling of deprioritized CG PDU when both cg-RetransmissionTimer and lch-basedPrioritization are configured |
CATT |
| R2-2101669 |
Corrections on the start of the configuredGrantTimer |
Beijing Xiaomi Mobile Software |
| R2-2102077 |
Report on [AT113-e][502][NR-U] CRs on NR-U User Plane (Ericsson) |
Ericsson |
| 6.3.3 |
Control plane |
|
| R2-2100183 |
Correction on RSSI and channel occupancy measurements |
Samsung Electronics Co., Ltd |
| R2-2100870 |
Discussion on NR-U RSSI/CO measurement |
Apple, xiaomi |
| R2-2100871 |
Clarification on NR-U RSSI measurement procedure |
Apple |
| R2-2101163 |
RRC corrections for NR-U |
ZTE Corporation, Sanechips |
| R2-2101164 |
Corrections to UE capability for NR-U (Rel-16) |
ZTE Corporation, Sanechips |
| R2-2101269 |
Correction to search space switch configuration |
Ericsson |
| R2-2101491 |
Correction on description of measResultForRSSI and of conditional presence SharedSpectrum |
Huawei, HiSilicon |
| R2-2102076 |
Report of [AT113-e][501][NR-U] CRs on NR-U Control Plane |
Qualcomm Incorporated |
| R2-2102082 |
Corrections on UE capability for NR-U |
ZTE Corporation, Sanechips |
| R2-2102085 |
Correction on RSSI and channel occupancy measurements |
Samsung, Ericsson |
| 6.4.1 |
General and Stage-2 corrections |
|
| R2-2100009 |
LS reply on SL CG handling (R1-2009460; contact: Ericsson) |
RAN1 |
| R2-2100010 |
LS on R16 V2X Mode-2 agreements to capture in MAC specification (R1-2009474; contact: Intel) |
RAN1 |
| R2-2100011 |
LS reply on RAN2 agreements and RAN1 related issues (R1-2009475; contact: Intel) |
RAN1 |
| R2-2100012 |
Reply LS on definition of NR V2X con-current operation (R1-2009491; contact: Huawei) |
RAN1 |
| R2-2100017 |
LS on configurable values for sl-DCI-ToSL-Trans (R1-2009577; contact: Ericsson) |
RAN1 |
| R2-2100022 |
Reply LS on UE capability for V2X (R1-2009635; contact: OPPO) |
RAN1 |
| R2-2100023 |
Reply LS on maximum data rate for NR sidelink (R1-2009643; contact: OPPO) |
RAN1 |
| R2-2100024 |
LS reply on RAN1 agreement on pre-emption (R1-2009661; contact: Intel) |
RAN1 |
| R2-2100061 |
LS on SL switching priority (R4-2017839; contact:Xiaomi) |
RAN4 |
| R2-2100073 |
Reply to LS C1-206576 on the re-keying procedure for NR SL (S3-203483; contact: LGE) |
SA3 |
| R2-2100687 |
CR for TS 38.300 for NR V2X on miscellaneous issues |
ZTE Corporation, Sanechips |
| R2-2102200 |
Reply LS on per-table MCS range for mode-2 (R1-2102017; contact: OPPO) |
RAN1 |
| R2-2102201 |
Reply LS on SL switching priority (R1-2102034; contact: Xiaomi) |
RAN1 |
| R2-2102202 |
LS on maximum data rate for NR sidelink (R1-2102137; contact: Samsung) |
RAN1 |
| R2-2102203 |
LS on SL HARQ-ACK reporting to the gNB (R1-2102176; contact: Ericsson) |
RAN1 |
| R2-2102276 |
CR for TS 38.300 for NR V2X on miscellaneous issues |
ZTE Corporation, Sanechips |
| R2-2102328 |
LS on the resource reservation period (R1-2101922; contact: LGE) |
RAN1 |
| 6.4.2 |
Control plane corrections |
|
| R2-2100115 |
Correction on reset configuration |
OPPO |
| R2-2100116 |
Clarification on the inter-frequency operation |
OPPO, Nokia, Nokia Shanghai Bell, Samsung Electronics, MediaTek Inc. |
| R2-2100118 |
Left issue on reset configuration |
OPPO |
| R2-2100150 |
Corrections to SL Resource Configuration |
Samsung Electronics Co., Ltd |
| R2-2100210 |
Correction on the Sidelink RRC Recofiguration Procedure |
CATT |
| R2-2100230 |
Correction on value range of sl-ConfigIndexCG |
OPPO |
| R2-2100231 |
Miscellaneous Correction on RRC spec for NR SL communication |
OPPO |
| R2-2100500 |
Miscellaneous corrections to TS 38.331 |
ZTE Corporation, Sanechips |
| R2-2100501 |
Corrections on the actions of measurement configuration in TS 38.331 |
ZTE Corporation, Sanechips |
| R2-2100502 |
Editorial corrections in TS 38.331 |
ZTE Corporation, Sanechips |
| R2-2100785 |
Lower layer indication in PC5 unicast link re-keying procedure |
vivo |
| R2-2100786 |
PC5-RRC connection release requested by upper layers |
vivo |
| R2-2100787 |
Clarification on SSB interval value 0 |
vivo |
| R2-2100788 |
Correction on T400 expiry behavior |
vivo |
| R2-2100789 |
Support RLC Re-establishment |
vivo |
| R2-2100790 |
Message protection for NR Sidelink |
vivo |
| R2-2100919 |
Clarficiations on RRC Parameter sl-ThresPSSCH-RSRP |
CATT |
| R2-2100976 |
Protection of sidelinkUEInformation and ULInformationTrasferIRAT |
Ericsson |
| R2-2100977 |
Protection of sidelinkUEInformation and ULInformationTrasferIRAT |
Ericsson |
| R2-2100978 |
Corrections regarding sidelink impacting NR |
Ericsson |
| R2-2101232 |
Clarification with respect to validity of configured SL grant type 1 received in HO command |
Nokia, Nokia Shanghai Bell |
| R2-2101234 |
Correction on SL configured grant type 1 validity under Uu RLF |
Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Qualcomm, CATT |
| R2-2101596 |
Miscellaneous corrections on 38.331 |
Xiaomi communications |
| R2-2101655 |
Correction on sl-MeasConfig configuration |
Google Inc. |
| R2-2101703 |
Clarification on DAPS HO configuration |
vivo |
| R2-2101740 |
Correction on SL LCP restriction of configured grant type 1 |
ASUSTeK |
| R2-2101760 |
Miscellaneous corrections on TS 36.331 (Rapportuer CR) |
Huawei, Hisilicon |
| R2-2101761 |
Miscellaneous corrections on TS 38.331 (Rapportuer CR) |
Huawei, Hisilicon |
| R2-2101767 |
CR on LCP restriction parameters for configured SL grant type1 |
Huawei, HiSilicon |
| R2-2101940 |
Correction on SL LCP restriction of configured grant type 1 |
ASUSTeK |
| R2-2102171 |
Miscellaneous corrections on TS 38.331 |
Huawei |
| R2-2102172 |
Correction on value range of sl-ConfigIndexCG and sl-HARQ-ProcID-offset |
Huawei, HiSilicon, OPPO |
| R2-2102174 |
Summary of [AT113-e][701][V2X] Miscellaneous corrections |
Huawei (Rapporteur) |
| R2-2102175 |
T400 expiry in timer table and protection of RRC messages |
vivo |
| R2-2102176 |
[Offline-702] [V2X] T400 expiry in timer table and protection of RRC message |
vivo (Rapporteur) |
| R2-2102177 |
Clarification on the inter-frequency operation |
OPPO, Nokia, Nokia Shanghai Bell, Samsung Electronics, MediaTek Inc. |
| R2-2102178 |
Correction on reset configuration |
OPPO |
| R2-2102179 |
Summary of ? [AT113-e][704][V2X/SL] Left issue on reset configuration (OPPO) |
OPPO |
| R2-2102181 |
Summary of [AT113-e][705][V2X/SL] RLC Re-establishment (vivo) |
vivo |
| R2-2102185 |
Correction on SL configured grant type 1 validity under Uu RLF |
Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Qualcomm, CATT |
| R2-2102188 |
Protection of sidelinkUEInformation and ULInformationTransferIRAT |
vivo |
| R2-2102195 |
Correction on SL configured grant type 1 validity under Uu RLF |
Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Qualcomm, CATT |
| R2-2102197 |
Correction on reset configuration |
OPPO |
| R2-2102240 |
Summary of RRC corrections in AI 6.4.2 |
Huawei, HiSilicon (Rapporteur) |
| R2-2102504 |
Correction on SL configured grant type 1 validity under Uu RLF |
Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Qualcomm, CATT |
| 6.4.3 |
User plane corrections |
|
| R2-2100098 |
Summary of email discussion [701][V2X] RAN1 related discussion (OPPO) |
OPPO |
| R2-2100099 |
CR on Correction on SL CG and mode2 operation |
OPPO |
| R2-2100117 |
Left issue on HARQ feedback for CG |
OPPO, vivo, Apple, InterDigital, Qualcomm, ZTE Corporation, Sanechips, CATT |
| R2-2100119 |
Miscellaneous Correction on NR-V2X |
OPPO |
| R2-2100120 |
Left issue with RAN1 impact |
OPPO |
| R2-2100211 |
Miscellaneous Correction on TS38.321 |
CATT |
| R2-2100212 |
Modification on the Formula of Calculating the SL_RESOURCR_RESELECTION_COUNTER's Range |
CATT |
| R2-2100213 |
Correction on the UL Threshold and SL Threshold |
CATT |
| R2-2100323 |
Clarification on the Notes for UL Prioritization |
CATT |
| R2-2100412 |
Cancellation of triggered SL-CSI reporting |
SHARP Corporation |
| R2-2100503 |
Miscellaneous corrections to TS 38.321 |
ZTE Corporation, Sanechips |
| R2-2100504 |
Corrections on LCP in TS 38.321 |
ZTE Corporation, Sanechips |
| R2-2100688 |
Correction on PDCP entity re-establishment |
ZTE Corporation, Sanechips |
| R2-2100791 |
Left issues on TX resource (re-)selection |
vivo, OPPO, Apple |
| R2-2100792 |
Clarification on sidelink process ID in SCI |
vivo |
| R2-2100793 |
Draft LS to RAN1 on HARQ process number in SCI |
vivo |
| R2-2100794 |
Draft LS to RAN1 on TX resource (re-)selection |
vivo |
| R2-2100861 |
Correction for HARQ Options for SL groupcast |
Apple |
| R2-2101068 |
Miscellaneous corrections to 38.321 |
Nokia, Nokia Shanghai Bell |
| R2-2101149 |
Correction to Uu DRX with sidelink |
Nokia, Nokia Shanghai Bell |
| R2-2101741 |
MAC Corrections for NR V2X |
ASUSTeK |
| R2-2101742 |
MAC Corrections for sidelink BSR triggering |
ASUSTeK |
| R2-2101925 |
Corrections on MCS selection |
Huawei, HiSilicon |
| R2-2102186 |
CR on Correction on SL CG and mode2 operation |
OPPO |
| R2-2102189 |
Miscellaneous MAC corrections |
LG Electronics Inc. |
| R2-2102190 |
Summary of email [AT113-e][711][V2X]SL CG related issues |
OPPO (rapporteur) |
| R2-2102191 |
[Draft] LS on HARQ feedback for CG |
OPPO |
| R2-2102192 |
Correction on resource re-selection |
vivo |
| R2-2102193 |
Summary of [AT113-e][713][V2X/SL] TX resource (re)selection w/ HARQ feedback consideration (vivo) |
vivo |
| R2-2102194 |
[AT113-e][710][V2X/SL] Miscellaneous MAC corrections (LG) |
LG Electronics Inc. (Rapporteur) |
| R2-2102196 |
Response LS to RAN1 on the resource reservation period |
RAN2 |
| R2-2102198 |
Correction on mode2 operation |
OPPO (Rapporteur) |
| R2-2102222 |
Review Report on MAC CRs in AI 6.4.3 |
LG Electronics Inc. (Rapporteur) |
| R2-2102260 |
Correction on resource re-selection |
vivo |
| R2-2102421 |
[Draft] Response LS to RAN1 on the resource reservation period |
LG Electronics Inc. |
| R2-2102422 |
Draft_38 321 _RAN2 specification update based on RAN1 LS |
LG Electronics Inc. |
| R2-2102505 |
Correction on mode2 operation |
OPPO (Rapporteur) |
| 6.4.4 |
UE capabilities |
|
| R2-2100114 |
Update on V2X UE capability |
OPPO |
| R2-2100923 |
Correction to UE actions related to reception of the UECapabilityEnquirySidelink |
Samsung Electronics, OPPO |
| R2-2101244 |
On the peer UE capability transfer in unicast sidelink |
Nokia, Nokia Shanghai Bell |
| 6.5 |
NR Industrial Internet of Things (IoT) |
|
| R2-2102317 |
Phase-1 Summary of Email Discussion [AT113-e][025] |
Nokia |
| 6.5.1 |
General and Stage-2 corrections |
|
| R2-2100026 |
Reply LS on Intra UE Prioritization Scenario (R1-2009680; contact: vivo) |
RAN1 |
| 6.5.2 |
RRC Corrections |
|
| R2-2100712 |
Configuration of AutonomousTX and cg-retransmission timer |
Nokia, Nokia Shanghai Bell |
| R2-2101340 |
Correction on the configuration of Type 1 configured grant |
Huawei, HiSilicon |
| R2-2101743 |
LCP restriction for allowedCG-List and configuredGrantType1Allowed |
ASUSTeK |
| R2-2101941 |
LCP restriction for allowedCG-List and configuredGrantType1Allowed |
ASUSTeK |
| 6.5.3 |
MAC Corrections |
|
| R2-2100219 |
Explicit discard of UL grants colliding with UL grants in RAR, or to TC-RNTI, or of MSGA payload |
CATT |
| R2-2100713 |
Clarification of conditions for autonomous transmission |
Nokia, Nokia Shanghai Bell |
| R2-2100714 |
Consideration of an uplink grant for prioritization |
Nokia, Nokia Shanghai Bell |
| R2-2100854 |
Clarification on HARQ process ID configuration |
Apple |
| R2-2100889 |
Correction on ignored uplink grant associated to RACH procedure_Alt1 |
OPPO |
| R2-2100890 |
Correction on ignored uplink grant associated to RACH procedure_Alt2 |
OPPO |
| R2-2101004 |
Correction for Uplink Grant Received in RAR and Addressed to Temporary C-RNTI (Option 1) |
Samsung, Ericsson, ZTE, Nokia, Huawei, HiSilicon |
| R2-2101005 |
Correction for Uplink Grant Received in RAR and Addressed to Temporary C-RNTI (Option 2) |
Samsung, Ericsson, ZTE, Nokia, CATT, Huawei, HiSilicon |
| R2-2101511 |
UL transmission scheduled with temporary C-RNTI or RAR grant |
LG Electronics Inc. |
| R2-2101529 |
CR on the configuredGrantTimer for deprioritized UL grant |
ZTE Corporation, Sanechips |
| R2-2101530 |
Discussion on timer control when configured grant transmission is canceled |
ZTE Corporation, OPPO |
| R2-2101744 |
Configured grant timer handling upon PUSCH cancellation for bundle case |
ASUSTeK |
| R2-2101745 |
MAC Corrections for NR IIOT CG confirmation |
ASUSTeK |
| R2-2101746 |
MAC Corrections for NR IIOT intra-UE prioritization |
ASUSTeK |
| R2-2102279 |
Report of Offline 023: IIOT User Plane I |
Samsung |
| R2-2102287 |
Correction on configuredGrantTimer handling on the deprioritized configured grant |
ZTE Corporation, Sanechips |
| R2-2102318 |
Phase-1 Summary of [AT113-e][024][IIOT] User Plane II (Asus) |
ASUSTeK |
| R2-2102438 |
Phase-2 Summary of [AT113-e][024][IIOT] User Plane II (Asus) |
ASUSTeK |
| R2-2102484 |
Correction for Uplink Grant Received in RAR and Addressed to Temporary C-RNTI |
Samsung, Ericsson, ZTE, Nokia, CATT, Huawei, HiSilicon |
| 6.5.4 |
PDCP Corrections |
|
| R2-2100220 |
The impact of drb-ContinueEHC-DL/UL configuration on PDCP specification |
CATT |
| R2-2101670 |
Corrections on the EHC reset |
Beijing Xiaomi Mobile Software |
| 6.6.1 |
General and Stage 2 corrections |
|
| R2-2100044 |
LS on Rel-16 NR Positioning Correction (R3-207220; contact: Huawei) |
RAN3 |
| R2-2100402 |
Miscellaneous corrections in TS38.305 |
CATT |
| R2-2101383 |
Activation Time for Periodic UL SRS Transmission |
Ericsson |
| R2-2101385 |
UE handling of Positioning Frequency Layer |
Ericsson |
| R2-2101829 |
Correction on the description for gNB measurements |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2101830 |
[Draft] Reply LS on Rel-16 NR Positioning Correction |
Huawei, HiSilicon |
| R2-2102106 |
Correction on the description for gNB measurements |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2102109 |
[Draft] Reply LS on Rel-16 NR Positioning Correction |
Huawei, HiSilicon |
| R2-2102126 |
Reply LS on Rel-16 NR Positioning Correction |
RAN2 |
| R2-2102226 |
Summary for stage2 corrections for NR Positioning |
Ericsson |
| R2-2102327 |
Reply LS on Rel-16 NR positioning Correction (R1-2101918; contact: Huawei) |
RAN1 |
| 6.6.2 |
RRC corrections |
|
| R2-2100151 |
Corrections to acquisition of positioning SIBs |
Samsung Electronics Co., Ltd, Ericsson |
| R2-2100403 |
Corrections on posSIB validity |
CATT,Ericsson, Intel Corporation, MediaTek Inc |
| R2-2100404 |
Correction on Positioning SRS Resource |
CATT |
| R2-2101386 |
Usage of ExpirationTime and ValueTag |
Ericsson |
| R2-2101832 |
Summary for POS RRC AI 6.6.2 |
Huawei, HiSilicon |
| R2-2101899 |
Correction on SI window calculation for PosSIB |
Samsung R&D Institute UK |
| R2-2102107 |
Corrections to acquisition of positioning SIBs |
Samsung Electronics Co., Ltd, Ericsson |
| R2-2102108 |
Correction on SI window calculation for PosSIB |
Samsung |
| R2-2102127 |
Corrections to acquisition of positioning SIBs |
Samsung Electronics, Ericsson |
| 6.6.3 |
LPP corrections |
|
| R2-2100405 |
Correction on NR-Multi-RTT-RequestAssistanceData |
CATT |
| R2-2100406 |
Corrections on the field description of commonIEsProvideAssistanceData in TS37.355 |
CATT |
| R2-2101382 |
Correction of A-GNSS Periodical retrival of Assistance Data |
Ericsson |
| R2-2101384 |
LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap |
Ericsson |
| R2-2101826 |
Disucussion on the need for fields in the uplink LPP message |
Huawei, HiSilicon |
| R2-2101827 |
Correction to the need code for downlink LPP message |
Huawei, HiSilicon |
| R2-2101828 |
Discussions on PRS configurations |
Huawei, HiSilicon |
| R2-2101858 |
Disucussion on the need for fields in the uplink LPP message |
Huawei, HiSilicon |
| R2-2101889 |
Summary of agenda item 6.6.3 - LPP Corrections |
Nokia, Nokia Shanghai Bell |
| R2-2102105 |
Summary of agenda item 6.6.3 - LPP Corrections |
Nokia, Nokia Shanghai Bell |
| R2-2102123 |
LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap |
Ericsson |
| R2-2102228 |
Discussions on PRS configurations |
Huawei, HiSilicon |
| R2-2102423 |
Discussions on PRS configurations |
Huawei, HiSilicon |
| R2-2102434 |
Corrections on the field description of commonIEsProvideAssistanceData in TS37.355 |
CATT |
| 6.7.1 |
General and Stage-2 Corrections |
|
| R2-2100027 |
LS on support of NUL and SUL during DAPS handovery (R1-2009682; contact: Intel) |
RAN1 |
| R2-2101519 |
Addition of releasing the source part of DAPS DRBS upon DAPS release |
LG Electronics France |
| R2-2102004 |
Addition of releasing the source part of DAPS DRBS upon DAPS release |
LG Electronics France |
| R2-2102306 |
Addition of releasing the source part of DAPS DRBS upon DAPS release |
LG Electronics France |
| 6.7.2 |
Conditional PSCell change for intra-SN and Conditional handover related corrections |
|
| R2-2100585 |
Clarification regarding CHO following IRAT HO failure |
Samsung Telecommunications |
| R2-2101263 |
Conditional handover for LTE-5GC |
Ericsson |
| R2-2101264 |
Missing release of VarConditionalReconfiguration |
Ericsson |
| R2-2101265 |
Inability to comply with conditional reconfiguration |
Ericsson |
| R2-2101266 |
Addition of conditional reconfiguration in measurement configuration description |
Ericsson |
| R2-2101362 |
Correction on NR Mobility Enhancement |
Apple |
| R2-2101363 |
Correction on LTE Mobility Enhancement |
Apple |
| R2-2101691 |
Discussion on some issues for CHO and CPC |
Huawei, HiSilicon, China Telecom |
| R2-2101900 |
Report of [Post112-e][254][R16 MOB] Issue on failure handling of handover without key change for the UE configured with attemptCondReconfig (Sharp) |
SHARP Corporation |
| R2-2101901 |
[Post112-e][254][R16 MOB] Clarification of behaviour to avoid security risk in CHO based recovery after handover without key change failure |
Sharp |
| R2-2101963 |
Summary of discussion [210][MOB] CHO/CPC corrections (Intel) |
Intel Corporation |
| R2-2101978 |
Non-support of CHO/CPC with LTE/5GC |
Ericsson |
| R2-2101979 |
Non-support of CHO/CPC with LTE/5GC |
Ericsson |
| R2-2101996 |
Inability to comply with conditional reconfiguration |
Ericsson |
| R2-2101997 |
Correction on NR Mobility Enhancement |
Huawei, HiSilicon, China Telecom |
| R2-2101998 |
Correction on LTE Mobility Enhancement |
Huawei, HiSilicon, China Telecom |
| R2-2101999 |
Correction on LTE Mobility Enhancement |
Apple, Ericsson |
| R2-2102169 |
Inability to comply with conditional reconfiguration |
Ericsson |
| R2-2102512 |
Correction on LTE Mobility Enhancement |
Apple, Ericsson |
| 6.7.3 |
UE capability corrections |
|
| R2-2101025 |
Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability |
Nokia, Nokia Shanghai Bell |
| R2-2101026 |
Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability |
Nokia, Nokia Shanghai Bell, MediaTek, Intel Corporation |
| R2-2101027 |
Dummifying the field intraFreqMultiUL-TransmissionDAPS |
Nokia, Nokia Shanghai Bell, MediaTek, Intel Corporation |
| R2-2101028 |
Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability |
Nokia, Nokia Shanghai Bell, MediaTek, Intel Corporation |
| R2-2101360 |
Clarification on DAPS HO Capability |
Apple |
| R2-2101710 |
Understanding of DAPS in BWC-A band |
Huawei, HiSilicon |
| R2-2101965 |
Summary of [AT113-e][212][MOB] UE capability corrections for LTE and NR mobility (Nokia) |
Nokia |
| R2-2102058 |
Report of [Post113-e][214][DAPS] Correction on inter-node signalling for DAPS UE capability coordination (Huawei) |
Huawei, HiSilicon |
| R2-2102347 |
Correction on inter-node signalling for DAPS UE capability coordination |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
| R2-2102349 |
Correction on inter-node signalling for DAPS UE capability coordination |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
| R2-2102361 |
Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability |
Nokia, Nokia Shanghai Bell, MediaTek, Intel Corporation |
| R2-2102446 |
Summary of [AT113-e][212][MOB] UE capability corrections for LTE and NR mobility (Nokia) |
Nokia |
| 6.8.1 |
General and Stage-2 Corrections |
|
| R2-2100021 |
LS on HARQ-ACK codebook configuration for secondary PUCCH group (R1-2009631; contact: Nokia) |
RAN1 |
| R2-2100058 |
LS on TCI state indication at Direct SCell activation (R4-2017329; contact: MediaTek) |
RAN4 |
| R2-2100059 |
LS on RAN4 agreements for MR-DC Idle mode CA measurements (R4-2017390; contact: ZTE) |
RAN4 |
| R2-2100062 |
LS response on cell-grouping UE capability for synchronous NR-DC (R4-2017847; contct: Apple) |
RAN4 |
| R2-2101088 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2101089 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2101400 |
CR on support of NR-DC within the same gNB-DU |
ZTE Corporation, Sanechips |
| R2-2101479 |
Corrections on UL power sharing |
Huawei, HiSilicon, ZTE Corporation (rapporteur) |
| R2-2101728 |
Corrections on UL power sharing |
vivo |
| R2-2101966 |
[AT113-e][220][DCCA] Stage-2, Fast Scell activation and early measurements (Nokia) |
Rapporteur (Nokia) |
| R2-2102002 |
CR on support of NR-DC within the same gNB-DU |
ZTE Corporation, Sanechips |
| R2-2102003 |
Corrections on UL power sharing |
Huawei, HiSilicon, ZTE Corporation (rapporteur) |
| R2-2102340 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2102341 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| 6.8.2 |
Corrections to Fast Scell activation and Early measurement reporting |
|
| R2-2100121 |
Correction for TCI state indication of direct SCell activation |
Qualcomm Incorporated |
| R2-2100127 |
Discussion on serving cell early measurement reporting |
Qualcomm Incorporated |
| R2-2100303 |
Corrections on condition of idle-inactive measurement configuration update |
OPPO |
| R2-2100304 |
Clarification on carrier frequency in MeasIdleConfigSIB |
OPPO |
| R2-2100305 |
Clarification on UE behaviour due to entering dormant BWP |
OPPO |
| R2-2100377 |
Discussion on serving cell early measurement reporting |
Qualcomm Incorporated |
| R2-2100563 |
Discussion on early measurement requirements |
ZTE Corporation, Sanechips |
| R2-2100564 |
CR to introduce new T331 timer value |
ZTE Corporation, Sanechips |
| R2-2100565 |
CR to introduce new capability for T331 timer value |
ZTE Corporation, Sanechips |
| R2-2100566 |
Reply LS on MR-DC Idle mode CA measurements |
ZTE Corporation, Sanechips |
| R2-2100567 |
Discussion on serving cell reporting for early measurement |
ZTE Corporation, Sanechips |
| R2-2101017 |
Correction on first active uplink BWP |
vivo |
| R2-2101073 |
CR on serving cell reporting |
Nokia, Nokia Shanghai Bell |
| R2-2101074 |
CR on T331 value range |
Nokia, Nokia Shanghai Bell |
| R2-2101075 |
TCI state indication at direct scell activation |
Nokia, Nokia Shanghai Bell |
| R2-2101090 |
Serving cell reporting in early measurements |
Ericsson |
| R2-2101500 |
Correction on BWP operation |
Samsung |
| R2-2101570 |
Clarification on sCellState configuration upon SCell modification |
ZTE Corporation, Sanechips |
| R2-2101692 |
Clarification on beam measurement and reporting based on broadcasted EMR configuration |
Huawei, HiSilicon |
| R2-2101693 |
Clarification on deriving and reporting cell level and beam level serving cell results |
Huawei, HiSilicon |
| R2-2101695 |
Discussion on TCI state indication at direct SCell activation |
Huawei, HiSilicon |
| R2-2101729 |
TCI state activation at Direct SCell activation |
vivo |
| R2-2101747 |
Correction on tci-PresentInDCI |
ASUSTeK |
| R2-2101851 |
TCI state indication for Direct SCell activation |
MediaTek Inc. |
| R2-2101853 |
TCI state for direct SCell activation |
MediaTek Inc. |
| R2-2101942 |
Correction on tci-PresentInDCI |
ASUSTeK |
| R2-2101968 |
Summary of [AT113-e][222][DCCA] Serving cell measurements and EMR requirements (ZTE) |
ZTE |
| R2-2102000 |
Correction on tci-PresentInDCI |
ASUSTeK |
| R2-2102001 |
Clarification on sCellState configuration upon SCell modification |
ZTE Corporation, Sanechips |
| R2-2102199 |
Reply LS on TCI state indication at Direct SCell activation (R1-2102015; contact: MediaTek) |
RAN1 |
| R2-2102344 |
CR on serving cell reporting |
Ericsson |
| R2-2102345 |
CR on serving cell reporting |
Ericsson |
| 6.8.3 |
Other DCCA corrections |
|
| R2-2100093 |
Correction on the Handling of Reconfiguration within RRC Resume |
CATT |
| R2-2100094 |
Correction on the Handling of Reconfiguration within RRC Resume |
CATT |
| R2-2100095 |
Clarification on HARQ-ACK codebook for secondary PUCCH group |
CATT |
| R2-2100096 |
Clarification on Fast MCG Link Recovery |
CATT |
| R2-2100097 |
Clarification on Fast MCG Link Recovery |
CATT |
| R2-2100438 |
T316 handling when rlf-TimersAndConstantsMCG-Failure is received |
Samsung, ZTE Corporation, Sanechips |
| R2-2101016 |
Correction on FR2 NR-DC power control parameter |
vivo |
| R2-2101018 |
Correction on the submission of RRCReconfigurationComplete |
vivo |
| R2-2101076 |
HARQ-ACK codebook configuration for secondary PUCCH group |
Nokia, Nokia Shanghai Bell |
| R2-2101091 |
Cell grouping for asynchronous NR-DC |
Ericsson |
| R2-2101092 |
Correction on p-UE-FR2 and p-NR-FR2 for NR-DC power control |
Ericsson |
| R2-2101093 |
Summary of [Post112-e][255][R16 DCCA] Cell grouping for synchronous NR-DC |
Ericsson |
| R2-2101694 |
NR-DC cell grouping for async and sync NR-DC |
Huawei, HiSilicon |
| R2-2101799 |
Discussion on cell group capability |
MediaTek Inc. |
| R2-2101967 |
Summary of [AT113-e][221][DCCA] Other DCCA corrections |
Ericsson (rapporteur) |
| R2-2101980 |
[AT113-e][223][DCCA] Asynchronous and synchronous NR-DC cell grouping (MediaTek) |
MediaTek |
| R2-2102010 |
Correction on the Handling of Reconfiguration within RRC Resume |
CATT |
| R2-2102210 |
Introduction of Cell Grouping UE capability for NR-DC |
Qualcomm Incorporated |
| R2-2102211 |
Introduction of Cell Grouping UE capability for NR-DC |
Qualcomm Incorporated |
| R2-2102212 |
[DRAFT] Introduction of Cell Grouping UE capability for NR-DC |
Qualcomm Incorporated |
| R2-2102342 |
Clarification on Fast MCG Link Recovery |
CATT |
| R2-2102343 |
Clarification on Fast MCG Link Recovery |
CATT |
| R2-2102346 |
Correction on the Handling of Reconfiguration within RRC Resume |
CATT |
| 6.9.3 |
Control plane Corrections |
|
| R2-2100456 |
CR on 38.331 for power saving |
vivo |
| R2-2102083 |
CR on 38.331 for power saving |
vivo |
| 6.10.1 |
General and stage-2 corrections |
|
| R2-2100037 |
Reply LS on QoS Monitoring for URLLC (R3-207177; contact: Ericsson) |
RAN3 |
| R2-2100045 |
LS to SA5 on MDT Stage 2 and Stage 3 alignment (R3-207222; contact: Ericsson) |
RAN3 |
| R2-2100077 |
LS Reply on QoS Monitoring for URLLC (S5-204537; contact: Intel) |
SA5 |
| R2-2100078 |
Reply LS on the user consent for trace reporting (S5-204542; contact: Huawei) |
SA5 |
| R2-2100692 |
Correction on the configuration effectiveness of Logged MDT |
vivo |
| R2-2100693 |
Miscellaneous corrections to TS 37.320 |
vivo |
| R2-2101416 |
On clarifications in stage-2 description |
Ericsson |
| R2-2101426 |
[Draft] Reply LS on MDT Stage 2 and Stage 3 alignment |
Ericsson |
| R2-2101592 |
Correction on time stamp for event triggered logged MDT |
ZTE Corporation, Sanechips |
| R2-2101651 |
Clarification on Average UE throughout measurement |
Samsung |
| R2-2102131 |
Merged Corrections to TS 37.320 |
CMCC, Nokia |
| R2-2102141 |
Report of [AT113-e][804][NR/R16 SON/MDT] Stage-2 corrections (CMCC, Nokia) |
CMCC, Nokia |
| R2-2102225 |
Summary for 6.10.1 General and stage-2 corrections |
CMCC |
| R2-2102274 |
Report of [AT113-e][803][NR SON/MDT] Editorial corrections of 38.331and 36.331 CR (CATT |
CATT |
| 6.10.2 |
TS 38.314 corrections |
|
| R2-2100694 |
Miscellaneous corrections to TS 38.314 |
vivo |
| R2-2101638 |
Summary for AI 6.10.2 TS 38.314 corrections |
CMCC |
| R2-2102132 |
Miscellaneous corrections to TS 38.314 |
vivo, CMCC |
| R2-2102330 |
Report of [Offline-805][SONMDT] L2 measurement corrections (vivo, CMCC) |
vivo, CMCC |
| 6.10.3 |
RRC corrections |
|
| R2-2100088 |
Miscellaneous Corrections on WLAN and BT for MDT in 36.331 |
CATT |
| R2-2100089 |
Miscellaneous Corrections on WLAN and BT for MDT in 36.331 |
CATT |
| R2-2100184 |
Corrections on mobility from NR failure for inter-RAT MRO EUTRA |
Samsung Electronics Co., Ltd |
| R2-2100185 |
Corrections on Mobility History Information in 38.331 |
CATT |
| R2-2100186 |
Miscellaneous Corrections for SON and MDT in 36.331 |
CATT |
| R2-2100187 |
Corrections on the Release of CEF/RLF/RA Report in 38.331 |
CATT |
| R2-2100188 |
Miscellaneous Corrections for SON and MDT in 38.331 |
CATT |
| R2-2100189 |
Correction on RLF Report for Re-connection |
CATT |
| R2-2100190 |
Correction on RLF Report for Re-connection |
CATT |
| R2-2100197 |
Correction on periodical logging in any cell selection state |
Samsung Electronics Co., Ltd |
| R2-2100198 |
Corrections on RLF report content determination for inter-RAT HO failure |
Samsung Electronics Co., Ltd |
| R2-2100199 |
Miscellaneous corrections on inter-RAT MRO |
Samsung Electronics Co., Ltd |
| R2-2100427 |
Correction on RLF Report Content Handover from NR to LTE Failure |
MediaTek Inc. |
| R2-2100448 |
Misalignment of LTE and NR on neighbour cell measurements logging in any cell selection state |
Samsung Electronics Co., Ltd |
| R2-2100583 |
Clarification on logged MDT for IRAT and non-SIB4 frequencies |
Samsung Telecommunications, Ericsson |
| R2-2100584 |
Correction on reporting of NR cells for CEF, RLF and logMDT |
Samsung Telecommunications, Ericsson |
| R2-2100607 |
Logged MDT Info extension |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2100608 |
Logged MDT Info extendibility (Solution 1) |
Nokia, Nokia Shanghai Bell |
| R2-2100609 |
Logged MDT Info extendibility (Solution 3) |
Nokia, Nokia Shanghai Bell |
| R2-2100610 |
Logged MDT Info extendibility (Solution 4) |
Nokia, Nokia Shanghai Bell |
| R2-2100695 |
Miscellaneous corrections to TS 38.331 on SON and MDT |
vivo |
| R2-2100696 |
Correction to TS 38.331 on logged MDT configuration |
vivo |
| R2-2100858 |
Corrections on RLF Report |
Apple |
| R2-2100859 |
Corrections on RLF Report |
Apple |
| R2-2100860 |
Correction on UE check of NW configuration of obtaining location information |
Apple, Qualcomm |
| R2-2100873 |
Cleanup on miscellaneous issues in SON/MDT |
Apple |
| R2-2100874 |
Correction on neighbor cell measurement results report in SON/MDT |
Apple |
| R2-2101099 |
Correction to MDT |
Google Inc. |
| R2-2101419 |
On open issues of RA report, MHI and logged MDT |
Ericsson |
| R2-2101420 |
ON RA Report extension possibilities |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2101421 |
On the lack measResultServingCell availability in Any Cell Selection state |
Ericsson |
| R2-2101425 |
On WLAN-BT-sensor configration related |
Ericsson |
| R2-2101688 |
Corrections on NR MDT and SON (Rapporteur CR) |
Huawei |
| R2-2101689 |
Corrections on NR MDT and SON (Rapporteur CR) |
Huawei |
| R2-2101690 |
Discussion on location issues for MDT and SON |
Huawei, HiSilicon |
| R2-2101714 |
Correction to logged MDT configuration in full configuration |
Google Inc. |
| R2-2101722 |
Discussion on some issues for MDT and SON |
Huawei, HiSilicon |
| R2-2101846 |
Corrections for RLF Report |
OPPO |
| R2-2101847 |
Corrections for SON&MDT Logging Capability |
OPPO |
| R2-2101848 |
Miscellaneous Corrections for SON&MDT |
OPPO |
| R2-2101938 |
Corrections for Cross-RAT RLF Report |
OPPO |
| R2-2101939 |
Corrections for Sensor |
OPPO |
| R2-2101943 |
Clarification on location configuration in MDT |
ZTE Corporation, Sanechips |
| R2-2102134 |
SReport of [AT113-e][801][NR/R16 SON/MDT] Merged 38.331 CR (Huawei, Ericsson) |
Huawei (Email rapporteur) |
| R2-2102136 |
Report of [AT113-e][802][NR/R16 SON/MDT] |
Ericsson |
| R2-2102138 |
Report of [AT113-e][803][NR/R17 SON/MDT] Editorial corrections of 38.331and 36.331 CR (CATT) |
CATT |
| R2-2102139 |
Controversial corrections on NR MDT and SON |
Ericsson |
| R2-2102140 |
Report of controversial corrections of 38.331(Ericsson) |
Ericsson |
| R2-2102272 |
Editorial corrections on SON and MDT |
CATT |
| R2-2102273 |
Miscl corrections on SON and MDT |
CATT, OPPO, vivo, Apple, Qualcomm Incorporated |
| R2-2102280 |
Corrections on NR MDT and SON |
Huawei, Ericsson |
| R2-2102286 |
Corrections on NR MDT and SON (Rapporteur CR) |
Huawei, Ericsson |
| R2-2102319 |
Corrections on EUTRA MDT and SON (Rapporteur CR) |
Ericsson, Huawei (Rapporteur) |
| R2-2102331 |
Corrections on EUTRA MDT and SON (Rapporteur CR) |
Ericsson, Huawei |
| R2-2102348 |
Corrections on EUTRA MDT and SON (Rapporteur CR) |
Ericsson, Huawei |
| R2-2102464 |
RA report and Logged MDT Info extendibility |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2102465 |
Corrections on NR MDT and SON |
Ericsson |
| R2-2102521 |
Corrections on EUTRA MDT and SON (Rapporteur CR) |
Ericsson, Huawei (Rapporteur) |
| 6.11.1 |
General and Stage-2 Corrections |
|
| R2-2101813 |
Correction on uplink transmission allowed without TA |
Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2102078 |
Summary of [AT113-e][503][2sRA] CRs on 2sRA User Plane and stage-2 (ZTE) |
Offline discussion Rapporteur (ZTE) |
| 6.11.2 |
User plane corrections |
|
| R2-2100349 |
Correction on Usage of RA-RNTI in 2-step RA procedure |
vivo |
| R2-2100350 |
Correction on UL-SCH resource in 2-step RA procedure |
vivo |
| R2-2101512 |
38321 CR Correction on available UL-SCH resource |
LG Electronics Inc. |
| R2-2101811 |
Correction on BSR for two-step RA |
Huawei, HiSilicon |
| R2-2101838 |
Conditions to stop an ongoing RA procedure |
Asia Pacific Telecom, FGI |
| R2-2101857 |
Conditions to stop an ongoing RA procedure |
Asia Pacific Telecom, FGI |
| R2-2102079 |
Correction on available UL-SCH resource |
LG Electronics Inc. |
| R2-2102513 |
Correction on available UL-SCH resource |
LG Electronics Inc. |
| 6.11.3 |
Control plane corrections |
|
| R2-2101059 |
Corrections to conditions for 2-step RA |
Lenovo, Motorola Mobility |
| R2-2101165 |
Correction for 2-step CFRA |
ZTE Corporation, Sanechips |
| R2-2101812 |
Correction on C-RNTI replacement for 2-step RA |
Huawei, HiSilicon |
| R2-2102080 |
Report of [AT113-e][504][2sRA] CRs on 2sRA Control Plane (Ericsson) |
Ericsson (Rapporteur) |
| R2-2102081 |
Correction on C-RNTI replacement for 2-step RA |
Huawei, HiSilicon |
| R2-2102084 |
Correction on C-RNTI replacement and conditions for 2-step RA |
Huawei, HiSilicon, Lenovo, Motorola Mobility, ZTE Corporation, Sanechips |
| 6.12 |
NR Other Control Plane WIs |
|
| R2-2100485 |
UAC parameter selection for NPN |
Ericsson |
| R2-2101029 |
Clarification on manufacturer based UE capability ID |
Nokia, Nokia Shanghai Bell |
| R2-2101030 |
Clarification on manufacturer based UE capability ID |
Nokia, Nokia Shanghai Bell |
| R2-2101031 |
Clarification on manufacturer based UE capability ID |
Nokia, Nokia Shanghai Bell |
| R2-2101193 |
Correction on stop condition of T320 and T325 |
ZTE corporation, Sanechips |
| R2-2101557 |
CR on the Parameters Selection |
ZTE Corporation, Sanechips |
| R2-2101654 |
Correction on SIB validity check |
Google Inc. |
| R2-2101704 |
Discussion on intra-frequency reselection |
Huawei, HiSilicon |
| R2-2101715 |
UAC parameter selection in case of UE allowed both on PLMN and CAG |
Qualcomm Incorporated |
| R2-2101849 |
Corrections for inter-RAT cell selection triggered by SNPN selection |
Asia Pacific Telecom, FGI |
| R2-2101850 |
Stop conditions of T320 & T325 in E-UTRA protocols |
Asia Pacific Telecom, FGI |
| R2-2101852 |
Stop conditions of T320 & T325 in NR protocols |
Asia Pacific Telecom, FGI |
| R2-2101854 |
Inter-RAT cell selection triggered by SNPN selection |
Asia Pacific Telecom, FGI |
| R2-2101891 |
Avoid UTRA capabilities forwarding in handover preparation |
Google Inc. |
| R2-2102011 |
Summary of [AT113-e][101] PRN Corrections |
Nokia |
| R2-2102021 |
Summary of [AT113-e][101] PRN Corrections |
Nokia |
| R2-2102022 |
CR on the Parameters Selection |
ZTE Corporation, Sanechips |
| R2-2102023 |
Correction to 38.331 on intra-frequency reselection |
Huawei, HiSilicon |
| R2-2102024 |
Stop conditions of T320 in NR protocols |
Asia Pacific Telecom, FGI, ZTE corporation, Sanechips |
| R2-2102032 |
Summary of [AT113-e][113][RACS] Corrections (Nokia) |
Nokia |
| R2-2102033 |
Summary of [AT113-e][114][SRVCC] Corrections (Google) |
Google |
| R2-2102046 |
UTRA capabilities forwarding in handover preparation |
Google Inc. |
| R2-2102275 |
Correction on intra-frequency reselection |
Huawei, HiSilicon |
| 6.14 |
NR Other R1 WIs |
|
| R2-2100014 |
Reply LS on full slot formats support in TDD UL-DL (R1-2009505; contact: Qualcomm) |
RAN1 |
| R2-2100015 |
LS on CBRA based Beam Failure Recovery (R1-2009519; contact: Apple) |
RAN1 |
| R2-2101856 |
DRAFT LS Reply to RAN1 on CBRA based Beam Failure Recovery |
Apple |
| R2-2102029 |
DRAFT LS Reply to RAN1 on CBRA based Beam Failure Recovery |
Apple |
| R2-2102047 |
LS Reply to RAN1 on CBRA based Beam Failure Recovery |
RAN2 |
| 6.14.1 |
User plane corrections |
|
| R2-2101364 |
Capability and Configuration for SpCell BFR |
Apple |
| R2-2101365 |
38.306 CR on SpCell BFR |
Apple |
| R2-2101366 |
RRC CR on SpCell BFR |
Apple |
| R2-2101367 |
MAC CR on SpCell BFR |
Apple |
| R2-2101485 |
Correction on PUCCH group for enhanced PUCCH Spatial Relation |
Huawei, HiSilicon |
| R2-2102025 |
Summary of offline 111 - eMIMO corrections |
Apple |
| R2-2102026 |
Introduction of the UE Capability for SpCell BFR Enhancement |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2102027 |
Introduction of UE Capability and Configuration for SpCell BFR Enhancement |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2102028 |
Introduction of the Configuration for SpCell BFR Enhancement |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2102030 |
Correction on PUCCH group for enhanced PUCCH Spatial Relation |
Huawei, HiSilicon |
| 6.14.2 |
Control plane corrections |
|
| R2-2101526 |
Extension of the time domain allocation indicator for CG type 1 with typeB repetition |
ZTE Corporation, Sanechips |
| R2-2101527 |
Correction on the UE capability of extension of TDRA indication for Configured UL Grant type 1 |
ZTE Corporation, Sanechips |
| R2-2102031 |
Report of [AT113-e][112][L1enh_URLLC] Corrections (ZTE) |
ZTE corporation, Sanechips |
| R2-2102241 |
Extension of the time domain allocation indicator for CG type 1 with typeB repetition |
ZTE Corporation, Sanechips,Huawei, HiSilicon |
| 6.15 |
NR Other R4 WIs |
|
| R2-2100007 |
Reply LS on number of configurable CSI-RS resources per MO (R1-2009448; contact: Intel) |
RAN1 |
| R2-2100025 |
LS on uplink Tx switching (R1-2009676; contact: China Telecom) |
RAN1 |
| R2-2100051 |
LS on additional DC location reporting for intra-band UL CA (R4-2011722; contact: Qualcomm) |
RAN4 |
| R2-2100052 |
LS on DC location reporting f or intra-band UL CA (R4-2016817; contact: Nokia) |
RAN4 |
| R2-2100090 |
Discussions on DC location reporting for intra-band UL CA |
CATT |
| R2-2100293 |
CR for the supported max date rate for uplink Tx switching |
China Telecommunication, huawei, HiSilicon |
| R2-2100342 |
DC location reporting for intra-band UL CA |
Ericsson |
| R2-2100387 |
DC location information reporting |
Intel Corporation |
| R2-2100411 |
Discussion on support of additional DC location reporting for intra-band UL CA |
Samsung Electronics Co., Ltd |
| R2-2100480 |
DC location reporting for intra-band UL CA |
Qualcomm Incorporated |
| R2-2100938 |
Discussion on DC location reporting |
vivo |
| R2-2100955 |
Signalling of UL CA DC location |
Nokia, Nokia Shanghai Bell |
| R2-2101353 |
Clarification on the MPE-prohibit timer |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2101463 |
A practical RRC based DC location reporting solution |
Apple Inc |
| R2-2101528 |
Correction to 38.321 on MPE P-MPR Report |
ZTE Corporation, Sanechips |
| R2-2101810 |
DC location reporting |
MediaTek Inc. |
| R2-2101893 |
Discussion on DC location report for intra-band UL CA |
ZTE corporation, Sanechips |
| R2-2101894 |
draft CR on introduction of DC location reporting for intra-band UL CA |
ZTE corporation, Sanechips |
| R2-2101910 |
On the signalling for additional DC location reporting |
Huawei, HiSilicon |
| R2-2102207 |
Uplink Tx DC location reporting for two carrier uplink CA |
Apple Inc |
| R2-2102208 |
Uplink Tx DC location reporting for two carrier uplink CA |
Apple Inc |
| R2-2102209 |
Reply on LS on DC location reporting for intra-band UL CA |
RAN2 |
| R2-2102227 |
Summary document for Tx DC Location Reporting in AI 6.15 |
Apple Inc |
| R2-2102300 |
Summary of [AT113-e][027][R4 Other] Miscellaneous (China Telecom) |
China Telecommunications |
| R2-2102301 |
CR for the supported max date rate for uplink Tx switching |
China Telecom, Huawei, HiSilicon, CATT |
| R2-2102302 |
Correction to 38.321 on MPE P-MPR Report |
China Telecom, ZTE Corporation, Sanechips, Apple, Nokia, Nokia Shanghai Bell |
| R2-2102308 |
Summary of [AT113-e][026][R4 Other] DC location Reporting (Apple) |
Apple Inc |
| R2-2102430 |
Summary of [AT113-e][026][R4 Other] DC location Reporting (Apple) |
Apple Inc |
| 6.16 |
NR Other |
|
| R2-2100080 |
Reply LS on energy efficiency (S5-205357; contact: Orange) |
SA5 |
| R2-2100484 |
Clarify the usage of voiceFallbackIndication for emergency service |
Ericsson |
| R2-2100560 |
Further discuss the usage of voiceFallbackIndication for Emergency Service Fallback |
ZTE Corporation, Sanechips |
| R2-2100561 |
CR to clarify the usage of voiceFallbackIndication for Emergency Services Fallback |
ZTE Corporation, Sanechips |
| R2-2100562 |
CR to introduce new capability for Emergency Services Fallback |
ZTE Corporation, Sanechips |
| R2-2100872 |
Cleanup on Overheating UAI reporting procedure |
Apple |
| R2-2100979 |
RRC processing delay for DL RRC segmentation |
Ericsson |
| R2-2101170 |
OverheatingAssistance Restriction Release Signalling in EN-DC |
Beijing Xiaomi Mobile Software |
| R2-2101243 |
Consideration on aperiodic CSI with secondary DRX |
CATT |
| R2-2101288 |
Complete message at handover NR to EN-DC |
Ericsson |
| R2-2101289 |
Release with Redirect in 2 steps |
Ericsson |
| R2-2101290 |
Release with Redirect in 2 steps |
Ericsson |
| R2-2101291 |
Release with Redirect in 2 steps |
Ericsson |
| R2-2101292 |
Release with Redirect in 2 steps |
Ericsson |
| R2-2101319 |
On combined RRC procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2101320 |
RRC processing delays for combined procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2101326 |
Additional security issue with duplicate detection |
Futurewei Technologies |
| R2-2101327 |
Draft running CR to TS 38.323 on additional security issue about duplicate detection |
Futurewei Technologies |
| R2-2101328 |
Draft running CR to TS 38.322 on additional security issue about duplicate detection |
Futurewei Technologies |
| R2-2101346 |
Impacting UE to optimise inter-node transfer of SCG overheating info |
Samsung Telecommunications, LG Electronics Inc. |
| R2-2101356 |
Summary of Email Report of [Post112-e][063][NR TEI16] RRC processing time with segmentation |
Apple |
| R2-2101357 |
NR RRC processing time with segmentation |
Apple |
| R2-2101358 |
LTE RRC processing time with segmentation |
Apple |
| R2-2101359 |
Draft LS to RAN5 on RRC processing time with segmentation |
Apple |
| R2-2101434 |
Summary of e-mail discussion on UE indication when it no longer experiences overheating |
Ericsson |
| R2-2101473 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson |
| R2-2101656 |
Correction on handling of overheatingAssistanceConfigForSCG when SCG is released |
Huawei, HiSilicon |
| R2-2101657 |
Release with redirection in 2 steps release |
Huawei, HiSilicon |
| R2-2101713 |
Clarification on the initiation of RNA update |
Huawei, HiSilicon |
| R2-2101734 |
Secondary DRX and aperiodic CSI |
Ericsson |
| R2-2102232 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2102233 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2102234 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2102235 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2102261 |
Summary of Email Report of [Post112-e][063][NR TEI16] RRC processing time with segmentation |
Apple |
| R2-2102333 |
Summary of [028][TEI16] Miscellaneous I (Apple) |
Apple |
| R2-2102378 |
Correction on handling of overheatingAssistanceConfigForSCG when SCG is released |
Huawei, HiSilicon |
| R2-2102382 |
Correction on complete message at handover from NR to EN-DC |
Ericsson |
| R2-2102383 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2102384 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2102385 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2102405 |
Clarification for aperiodic CSI and secondary DRX group |
Ericsson |
| R2-2102470 |
NR RRC processing time with segmentation |
Apple |
| R2-2102471 |
LTE RRC processing time with segmentation |
Apple |
| R2-2102472 |
Draft LS to RAN5 on RRC processing time with segmentation |
Apple |
| R2-2102474 |
Phase 2 Summary of [028][TEI16] Miscellaneous I (Apple) |
Apple |
| R2-2102485 |
Summary of [AT113-e][029][TEI16] Miscellaneous II (Ericsson) |
Ericsson |
| R2-2102487 |
Phase 2 Summary of [028][TEI16] Miscellaneous I (Apple) |
Apple |
| R2-2102488 |
LS to RAN5 on RRC processing time with segmentation |
RAN2 |
| R2-2102508 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2102509 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| 7.1.2 |
Feature Lists and UE capabilities |
|
| R2-2100005 |
LS on updated Rel-16 RAN1 UE features lists for LTE (R1-2009351; contact: NTT DOCOMO, AT&T) |
RAN1 |
| 7.2.1 |
General and Stage-2 corrections |
|
| R2-2100072 |
Reply LS on early UE capability retrieval for eMTC (S2-2009345; contact: Qualcomm) |
SA2 |
| R2-2102205 |
LS on timing of neighbor cell RSS-based measurements (R4-2103657; contact: Qualcomm) |
RAN4 |
| R2-2102206 |
LS related to RSS based RSRQ for LTE-MTC (R4-2103728; contact: Huawei) |
RAN4 |
| 7.2.2 |
Connection to 5GC corrections |
|
| R2-2100932 |
Discussion for clarification on SIB acquisition for UE in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2100936 |
Clarification on SIB acquisition for UE in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2101036 |
Clarification to the DRX cycle in RRC_IDLE and RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2101038 |
System information change notification in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2101039 |
Correction to UAC parameters acquisition |
Huawei, HiSilicon |
| R2-2101155 |
SIB acquisition by eMTC UE in RRC-INACTIVE |
Qualcomm Incorporated |
| R2-2101467 |
Clarification of SI acquisition for UEs configured with eDRX in RRC_INACTIVE |
Ericsson LM |
| R2-2102062 |
Report of [AT113-e][402][eMTC R16] SIB change notification in RRC_INACTIVE (ZTE) |
ZTE (email discussion rapporteur) |
| R2-2102063 |
Summary of Offline 403 – UAC parameters acquisition |
Huawei |
| R2-2102066 |
Clarification on SIB change notification in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2102067 |
Clarification to the DRX cycle in RRC_IDLE and RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2102068 |
Correction to UAC parameters acquisition |
Huawei, HiSilicon |
| R2-2102070 |
Clarification to the DRX cycle in RRC_IDLE and RRC_INACTIVE |
Huawei, HiSilicon |
| 7.2.3 |
Other corrections |
|
| R2-2100735 |
PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling |
Qualcomm Incorporated |
| R2-2101040 |
Correction to SIB29 acquisition |
Huawei, HiSilicon |
| R2-2102064 |
[AT113-e][404][eMTC R16] PDCCH-based HARQ-ACK for multi-TB scheduling |
Qualcomm Incorporated |
| R2-2102065 |
Summary of offline 405 – SIB29 acquisition |
Huawei |
| R2-2102069 |
PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling |
Qualcomm Inc. |
| 7.3.2 |
UE-group wake-up signal (WUS) Corrections |
|
| R2-2100943 |
Discussion for correction on paging narrowband selection |
ZTE Corporation, Sanechips |
| R2-2100957 |
Correction on paging narrowband selection-Option 1 |
ZTE Corporation, Sanechips |
| R2-2100959 |
Correction on paging narrowband selection-Option 1 |
ZTE Corporation, Sanechips |
| R2-2100965 |
Correction on paging narrowband selection-Option 1 |
ZTE Corporation, Sanechips |
| R2-2100966 |
Correction on paging narrowband selection-Option 2 |
ZTE Corporation, Sanechips |
| R2-2100968 |
Draft LS to RAN3 on UE radio capability provision |
ZTE Corporation, Sanechips |
| R2-2101037 |
Paging monitoring in RRC_INACTIVE for GWUS capable Ues |
Huawei, HiSilicon |
| R2-2101152 |
Paging narrowband/carrier selection after RRC connection release |
Qualcomm Incorporated |
| R2-2101153 |
[draft] LS on parameters needed at paging RAN node to reliably page an eMTC UE in RRC-INACTIVE state |
Qualcomm Incorporated |
| R2-2101154 |
Paging narrowband selection in RRC-INACTIVE state |
Qualcomm Incorporated |
| R2-2101548 |
Paging narrowband selection in RRC_INACTIVE for LTE-M |
Ericsson |
| R2-2101549 |
Correction to paging narrowband selection in RRC_INACTIVE for LTE-M |
Ericsson |
| R2-2102152 |
Report of [AT113-e][302][eMTC R16] Paging narrowband selection (ZTE) |
ZTE (email discussion rapporteur) |
| R2-2102159 |
Correction on paging narrowband selection |
ZTE Corporation, Sanechips, Ericsson |
| 7.3.3 |
Transmission in preconfigured resources corrections |
|
| R2-2101033 |
Summary of email discussion [351] (N)RSRP reference for TA validation for PUR |
Huawei |
| R2-2101034 |
Clarification on the (N)RSRP reference for TA validation for PUR |
Huawei, HiSilicon |
| R2-2101035 |
Clarification on the (N)RSRP reference for TA validation for PUR |
Huawei, HiSilicon |
| R2-2101085 |
Correction on Drb-ContinueROHC for UP-PUR |
vivo |
| R2-2101550 |
Timing alignment validation for transmission using PUR |
Ericsson |
| R2-2101551 |
Correction to timing alignment validation for transmission using PUR |
Ericsson |
| R2-2102153 |
Summary of [AT113-e][303][NBIOT/eMTC R16] PUR corrections (Huawei) |
Huawei |
| R2-2102160 |
Clarification on TA validation for PUR |
Huawei, HiSilicon, Qualcomm Inc. |
| R2-2102161 |
Clarification on TA validation for PUR |
Huawei, HiSilicon, Qualcomm Inc. |
| R2-2102162 |
Correction on Drb-ContinueROHC for UP-PUR |
vivo |
| 7.4.2 |
DAPS handover Corrections |
|
| R2-2100486 |
Inter-node signalling for UE capability coordination in DAPS handover |
Ericsson |
| R2-2100487 |
No support of SUL during DAPS handover |
Ericsson, ZTE, Sanechips |
| R2-2100488 |
Reconfiguration during DAPS HO |
Ericsson |
| R2-2100525 |
NUL and SUL in DAPS handover |
Nokia, Nokia Shanghai Bell |
| R2-2100617 |
Handling of CHO configuration during DAPS HO |
Intel Corporation |
| R2-2100618 |
DAPS capability coordination between source and target |
Intel Corporation |
| R2-2100619 |
Support of DAPS handover without key change |
Intel Corporation, Ericsson |
| R2-2100620 |
Support of NUL and SUL during DAPS handover |
Intel Corporation, Huawei, HiSilicon |
| R2-2100626 |
Miscellaneous corrections for Mobility Enhancements |
Intel Corporation (Rapporteur), Ericsson |
| R2-2100627 |
38.331 CR on support of NUL and SUL during DAPS handover |
Intel Corporation, Huawei, HiSilicon |
| R2-2100628 |
38.300 CR on support of NUL and SUL during DAPS handover |
Intel Corporation, Huawei, HiSilicon |
| R2-2101101 |
Handling of non-DAPS bearers during DAPS HO |
MediaTek Inc. |
| R2-2101361 |
Clarification on SUL during DAPS HO |
Apple |
| R2-2101497 |
CR for handling of unforeseen protocol data during DAPS HO |
Samsung |
| R2-2101498 |
Handling of unforeseen protocol data during DAPS handover |
Samsung |
| R2-2101499 |
Correction on PDCP transmit operation |
Samsung |
| R2-2101501 |
Views on several security concerns for DAPS handover |
Samsung |
| R2-2101533 |
Corrections for DAPS Handover |
MediaTek Inc. |
| R2-2101534 |
Corrections for DAPS Handover |
MediaTek Inc. |
| R2-2101568 |
Corrections to DAPS handover in LTE |
ZTE Corporation, Sanechips |
| R2-2101569 |
Clarification on no support of SUL with DAPS |
ZTE Corporation, Sanechips, Ericsson |
| R2-2101579 |
DAPS HO without security key change |
LG Electronics Inc. |
| R2-2101711 |
Discussion on source release indication |
Huawei, HiSilicon |
| R2-2101712 |
Discussion on inter-node signalling for DAPS UE capability coordination |
Huawei, HiSilicon, MediaTek Inc., Qualcomm Incorporated, China Telecom, China Unicom |
| R2-2101902 |
Potential security issue on DAPS handover with key change failure |
SHARP Corporation |
| R2-2101964 |
Summary of [AT113-e][211][MOB] DAPS corrections (Huawei) |
Huawei |
| R2-2101971 |
Report of [AT113-e][211][MOB] Note to clarify non-DAPS bearer (MediaTek) |
MediaTek |
| R2-2101972 |
Note to clarify UE handling of non-DAPS bearer |
MediaTek Inc. |
| R2-2101976 |
Clarification on no support of SUL with DAPS |
Ericsson, ZTE Corporation, Sanechips |
| R2-2101977 |
Support of NUL and SUL during DAPS handover |
Intel Corporation, Huawei, HiSilicon |
| R2-2102006 |
Correction on PDCP transmit operation |
Samsung |
| R2-2102007 |
Corrections for DAPS Handover |
MediaTek Inc. |
| R2-2102479 |
Corrections for DAPS Handover |
MediaTek Inc., Intel (Rapporteur), Ericsson |
| 7.5 |
LTE Other WIs |
|
| R2-2100443 |
BufferSize reconfiguration for UDC after RRC connection re-establishment |
MediaTek Inc. |
| R2-2100606 |
Clarification to Fallback band combination definition |
Nokia, Nokia Shanghai Bell |
| R2-2101476 |
Redirection with MPS Indication |
Perspecta Labs, CISA ECD, T-Mobile, Ericsson |
| R2-2101665 |
Correction on SCG overheating configuration release |
Google Inc. |
| R2-2101985 |
BufferSize reconfiguration for UDC after RRC connection re-establishment |
MediaTek Inc. |
| 8.1 |
NR Multicast |
|
| R2-2101625 |
Discussion on L2 architecture |
CMCC |
| 8.1.1 |
Organizational, Requirements, Scope and Architecture |
|
| R2-2100032 |
Response LS on RAN impact of FS_5MBS Study (R3-207059; contact: Nokia) |
RAN3 |
| R2-2100071 |
LS on 5MBS progress and issues to address (S2- 2009235; contact: Huawei) |
SA2 |
| R2-2100082 |
Discussion on Requirement and Architecture of MBS |
CATT |
| R2-2100130 |
RRC state control for MBS reception |
OPPO |
| R2-2100174 |
L2 structure for NR MBS transmission |
MediaTek Inc. |
| R2-2100318 |
NR Multicast and Broadcast Radio Bearer Architecture aspects |
Qualcomm Inc |
| R2-2100353 |
MBS Protocol Architecture and Logical Channel Aggregation |
Futurewei |
| R2-2100803 |
Further consideration of control plane aspects for NR MBS |
Kyocera |
| R2-2100937 |
Discussion on L2 User Plane for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2101006 |
Layer-2 Structure for MBS |
Samsung |
| R2-2101007 |
MBS Radio Bearer (MRB) Type |
Samsung |
| R2-2101010 |
Updated NR MBS workplan |
Huawei, CMCC, HiSilicon |
| R2-2101051 |
MBS L2 Architecture, Control Plane and SA2 LS Discussion |
Intel Corporation |
| R2-2101139 |
MBS L2 architecture |
Lenovo, Motorola Mobility |
| R2-2101185 |
Discussion on the SA2 LS and the reply LS |
Huawei, HiSilicon |
| R2-2101215 |
General aspects of NR MBS |
ZTE, Sanechips |
| R2-2101718 |
38.300 Running CR for MBS in NR |
CMCC |
| R2-2101719 |
Discussion on SA2 LS on 5MBS Progress and Issues to address |
CMCC |
| R2-2101720 |
Reply LS to SA2 on 5MBS Progress and Issues to address |
CMCC |
| R2-2101730 |
Discussion on L2 architecture |
CMCC |
| R2-2101735 |
Data inactivity during MBS reception |
Ericsson |
| R2-2101860 |
Discussion on overall architecture of MBS traffic delivery |
LG Electronics Inc. |
| R2-2102253 |
38.300 Running CR for MBS in NR |
CMCC |
| R2-2102307 |
Report of [Offline-037][MBS] MBS General (Huawei) |
Huawei, HiSilicon |
| R2-2102463 |
38.300 Running CR for MBS in NR |
CMCC, Huawei |
| R2-2102480 |
Reply LS on 5MBS progress and issues to address |
RAN2 |
| R2-2102482 |
Report of [Offline-037][MBS] MBS General (Huawei) |
Huawei, HiSilicon |
| R2-2102503 |
38.300 Running CR for MBS in NR |
CMCC, Huawei |
| 8.1.2.1 |
Reliability |
|
| R2-2100083 |
Reliability Improvement for PTM Transmission |
CATT |
| R2-2100131 |
Discussion on reliability for MBS reception |
OPPO |
| R2-2100172 |
HARQ operation to improve reliability for PTM transmission |
MediaTek Inc. |
| R2-2100319 |
NR Multicast PTM bearer RLC AM mode operation |
Qualcomm Inc, FirstNet,British Telecom,UIC, Kyocera,BBC, AT&T |
| R2-2100322 |
Email discussion report for [Post112-e][071][MBS] UP Performance |
Qualcomm Inc |
| R2-2100354 |
L2 Retransmission (PDCP vs. RLC) for MBS |
Futurewei |
| R2-2100355 |
ARQ of PTM with Logical Channel Aggregation |
Futurewei |
| R2-2100370 |
PDCP Operation for MBS |
Nokia, Nokia Shanghai Bell |
| R2-2100372 |
Handling of Measurement Gaps |
Nokia, Nokia Shanghai Bell |
| R2-2100676 |
Discussion on reliability of MBS transmission |
Spreadtrum Communications |
| R2-2100761 |
Bearers for MBS Transmission |
Sharp |
| R2-2100832 |
Reliability for MBS Service |
vivo |
| R2-2100940 |
Discussion on L2 user plane reliability for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2101008 |
RLC AM for PTM |
Samsung |
| R2-2101011 |
Reliability enhancement for NR MBS |
Huawei, CBN, HiSilicon |
| R2-2101049 |
Complexity analysis for reliability enhancement in RLC and PDCP |
Intel Corporation |
| R2-2101120 |
Issues on MBS reliability |
Lenovo, Motorola Mobility |
| R2-2101172 |
Reliability and Dynamic Switch for MBS |
Ericsson |
| R2-2101216 |
Consideration on MBS reliability guarantee |
ZTE, Sanechips |
| R2-2101316 |
MBS Reliability |
InterDigital |
| R2-2101372 |
Consideration on the MBS transmission reliability |
Apple |
| R2-2101626 |
Discussion on MBS Reliability issues |
CMCC |
| R2-2101649 |
On reliability enhancement for NR multicast and broadcast |
Convida Wireless |
| R2-2101677 |
PDCP retransmission for PTM |
Beijing Xiaomi Mobile Software |
| R2-2101861 |
Discussion on reliability improvement and UL feedback in NR multicast |
LG Electronics Inc. |
| R2-2102313 |
[Offline-038][MBS] UP Architecture Decisions |
Chairman |
| 8.1.2.2 |
Dynamic PTM PTP switch with service continuity |
|
| R2-2100084 |
Open Issues on Dynamic PTM and PTP Switch |
CATT |
| R2-2100173 |
Dynamic PTM-PTP switch |
MediaTek Inc. |
| R2-2100321 |
Enhancements for supporting loss less switch between PTM and PTP RLC legs |
Qualcomm Inc |
| R2-2100356 |
Service Continuity during Dynamic PTM/PTP Switch with Logical Channel Aggregation |
Futurewei |
| R2-2100506 |
Consideration on dynamic switch between PTP and PTM |
Shanghai Jiao Tong University |
| R2-2100643 |
MBS split bearer configuration and PTP/PTM switching |
Nokia, Nokia Shanghai Bell |
| R2-2100677 |
Discussion on dynamic PTM PTP switch |
Spreadtrum Communications |
| R2-2100709 |
DL PDCP SN alignment issue |
NEC |
| R2-2100760 |
Support of dynamic switch between PTP and PTM |
Sharp |
| R2-2100825 |
The counting scheme for dynamically switching PTM and PTP |
ITRI |
| R2-2100833 |
Dynamic PTM PTP switch for RRC Connected UE |
vivo |
| R2-2100898 |
Security keys considering PTP/PTM switch for delivery mode 1/2 |
Sony |
| R2-2100942 |
Dynamic switch between PTM and PTP with service continuity |
CHENGDU TD TECH LTD. |
| R2-2100988 |
Dynamic PTM PTP switching |
LG Electronics Inc. |
| R2-2101012 |
Support of dynamic switch between PTP and PTM |
Huawei, CBN, HiSilicon |
| R2-2101143 |
MBS dynamic switch between PTP and PTM with service continuity |
Lenovo, Motorola Mobility |
| R2-2101217 |
Mode switching for NR MBS |
ZTE, Sanechips |
| R2-2101317 |
PTM/PTP mode switching |
InterDigital |
| R2-2101373 |
Dynamic PTM PTP switch with service continuity |
Apple |
| R2-2101605 |
Dynamic PTM/PTP Switching |
Convida Wireless |
| R2-2101627 |
Discussion on Dynamic PTP and PTM switch |
CMCC |
| R2-2101758 |
Dynamic switch between PTM and PTP for service continuity |
Intel Corporation |
| 8.1.2.3 |
Mobility with Service continuity |
|
| R2-2100085 |
Open Issues on Mobility with Service Continuity |
CATT, CBN |
| R2-2100133 |
Discussion on mobility with MBS Service continuity |
OPPO |
| R2-2100414 |
NR Multicast Broadcast mobility enhancements with service continuity |
Qualcomm Inc |
| R2-2100450 |
Mobility with Service Continuity |
Samsung |
| R2-2100630 |
Handling MBS during a CHO |
Futurewei |
| R2-2100644 |
MBS Mobility with Service Continuity |
Nokia, Nokia Shanghai Bell |
| R2-2100678 |
Discussion on service continuity during mobility |
Spreadtrum Communications |
| R2-2100834 |
Lossless Handover for MBS |
vivo |
| R2-2100835 |
MBS Service Continuity for RRC Connected UE |
vivo |
| R2-2100899 |
Standalone MRB for delivery mode 1 and RLM |
Sony |
| R2-2100944 |
Discussion on mobility with service continuity |
CHENGDU TD TECH LTD. |
| R2-2100991 |
Mobility with service continuity |
LG Electronics Inc. |
| R2-2101050 |
MBS service continuity in mobility |
Intel Corporation |
| R2-2101140 |
Connected Mode Mobility with Service Continuity |
Lenovo, Motorola Mobility |
| R2-2101144 |
HO for NR MBS |
MediaTek Inc. |
| R2-2101171 |
Mobility for NR MBS |
Ericsson |
| R2-2101187 |
Service continuity during inter-cell mobility |
Huawei, HiSilicon |
| R2-2101218 |
Lossless handover support for NR MBS |
ZTE, Sanechips |
| R2-2101374 |
Mobility with service continuity |
Apple |
| R2-2101628 |
Discussion on Mobility with service Continuity |
CMCC |
| R2-2101678 |
Packet loss at the PDCP reestablishment of RLC UM |
Beijing Xiaomi Mobile Software |
| R2-2101679 |
Support of DAPS handover for PTM MBS |
Beijing Xiaomi Mobile Software |
| 8.1.2.4 |
Other |
|
| R2-2100086 |
Discussion on Group Scheduling |
CATT |
| R2-2100132 |
Discussion on group based scheduling for MBS |
OPPO |
| R2-2100176 |
PTM scheduling for NR MBS |
MediaTek Inc. |
| R2-2100361 |
MBS MAC layer and group scheduling aspects |
Intel Corporation |
| R2-2100371 |
Miscellaneous Aspects of MBS |
Nokia, Nokia Shanghai Bell |
| R2-2100435 |
Considerations on Group Scheduling and Multiplexing Aspects |
Samsung |
| R2-2100505 |
Consideration on Group Scheduling Aspects |
Shanghai Jiao Tong University |
| R2-2100836 |
Group Scheduling for MBS |
vivo |
| R2-2100958 |
RAN2 related aspects for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2100989 |
MBS configuration for RRC_CONNECTED |
LG Electronics Inc. |
| R2-2101013 |
High layer aspects for group scheduling |
Huawei, HiSilicon |
| R2-2101060 |
Considerations on measurements for NR MBS in idle/inactive |
Lenovo, Motorola Mobility |
| R2-2101173 |
Aspects of Group Sscheduling |
Ericsson |
| R2-2101219 |
Group scheduling for NR MBS |
ZTE, Sanechips |
| R2-2101375 |
MBS reception in CONNECTED state |
Apple |
| R2-2101680 |
Slow-moving PDCP reception window issue |
Beijing Xiaomi Mobile Software |
| R2-2102249 |
Summary for MBS Group Scheduling under Agenda Item 8.1.2.4 |
vivo |
| 8.1.3 |
Idle and Inactive mode UEs |
|
| R2-2100087 |
Open Issues on MBS Reception for Idle and Inactive UEs |
CATT, CBN |
| R2-2100134 |
Discussion on MBS interesting indication and service continuity for delivery mode 2 |
OPPO |
| R2-2100135 |
Discussion on beam sweeping transmission for delivery mode 2 |
OPPO |
| R2-2100175 |
Common frequency resource for NR PTM transmission |
MediaTek Inc. |
| R2-2100177 |
Email Report of [Post112-e][069][MBS] Delivery mode 2 |
MediaTek Inc. |
| R2-2100320 |
NR Multicast-Broadcast services and configuration for UEs in different RRC states |
Qualcomm Inc |
| R2-2100451 |
NR MBS in Idle/Inactive mode |
Samsung |
| R2-2100631 |
Discussion on NR MBS solutions of mode 2 delivery |
Futurewei |
| R2-2100675 |
Discussion on MBS session delivery mode |
Spreadtrum Communications |
| R2-2100679 |
MBS session in Idle and Inactive mode |
Spreadtrum Communications |
| R2-2100837 |
MBS in Idle and Inactive Mode |
vivo |
| R2-2100960 |
Control plane for delivery mode 2 for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2100963 |
Simultaneous MBS and Unicast Operation in Idle/inactive Mode |
TCL Communication Ltd. |
| R2-2100990 |
MBS in IDLEINACTIVE |
LG Electronics Inc. |
| R2-2101080 |
MBS Idle |
Nokia, Nokia Shanghai Bell |
| R2-2101141 |
Discussion on MBS delivery modes |
Lenovo, Motorola Mobility |
| R2-2101186 |
On the general aspects for delivery mode 1 and 2 |
Huawei, HiSilicon |
| R2-2101188 |
MBS configuration for delivery mode 2 |
Huawei, HiSilicon |
| R2-2101220 |
Delivery mode 2 for NR MBS |
ZTE, Sanechips |
| R2-2101376 |
MBS reception in IDLE/INACTIVE state |
Apple |
| R2-2101495 |
NR MBS Configuration Information |
Convida Wireless |
| R2-2101594 |
PTM configuration for NR MBS |
TCL Communication Ltd. |
| R2-2101606 |
On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs |
Convida Wireless |
| R2-2101629 |
Discussion on delivery mode 2 |
CMCC |
| R2-2101681 |
Combination of service continuity and counting for delivery mode 2 |
Beijing Xiaomi Mobile Software |
| R2-2101682 |
Beam association for MCCH and MCCH change notification |
Beijing Xiaomi Mobile Software |
| R2-2101736 |
MBS and Idle and Inactive mode UEs |
Ericsson |
| R2-2101737 |
Multicast in Idle and Inactive |
Ericsson |
| R2-2101759 |
MBS support for delivery mode 2 |
Intel Corporation |
| R2-2101892 |
Discussion on MBS Control Information Configuration |
TCL Communication Ltd. |
| R2-2101903 |
L2 architecture for delivery mode 2 |
SHARP Corporation |
| 8.2.1 |
Organizational, Requirements and Scope |
|
| R2-2101480 |
Work plan for Rel-17 Further Multi-RAT Dual-Connectivity enhancements |
Huawei |
| 8.2.2 |
Efficient activation / deactivation mechanism for one SCG and SCells |
|
| R2-2100136 |
Discussion on SCG deactivation and activation |
OPPO |
| R2-2100137 |
Discussion on TRS activation for fast SCell activation |
OPPO |
| R2-2100426 |
Discussion on SCG deactivation |
China Telecom |
| R2-2100568 |
Further consideration on SCG deactivation and activation |
ZTE Corporation, Sanechips |
| R2-2100589 |
Progressing SCG deactivation and resumption for R17 |
Samsung Telecommunications |
| R2-2100632 |
Further discuss the issues with SCG fast activation |
Futurewei |
| R2-2100640 |
Further considerations on SCG deactivation |
NEC |
| R2-2100641 |
SCG (de)activation initiation |
NEC |
| R2-2100647 |
Considerations on Time Alignment Timer for SCG deactivation |
KDDI Corporation |
| R2-2100667 |
Discussion on efficient activation mechanism for one SCG and SCells |
Spreadtrum Communications |
| R2-2100729 |
Power-efficient SCG (De)activation mechanism |
LG Electronics |
| R2-2100730 |
Time-fficient SCG (De)activation mechanism |
LG Electronics |
| R2-2101014 |
UE behavior for SCG deactivation |
vivo |
| R2-2101015 |
Signaling aspect of SCG activation and deactivation |
vivo |
| R2-2101077 |
Deactivated SCG handling |
Nokia, Nokia Shanghai Bell |
| R2-2101078 |
MN and SN responsibilities for SCG deactivation |
Nokia, Nokia Shanghai Bell |
| R2-2101094 |
Mobility and RRM for deactivated SCG |
Ericsson |
| R2-2101095 |
On the need for random access during SCG activation |
Ericsson |
| R2-2101096 |
SCG (de)activation procedure |
Ericsson |
| R2-2101121 |
General issues on SCG activation and deactivation |
Lenovo, Motorola Mobility |
| R2-2101122 |
[Draft] LS on SCG activation and deactivation |
Lenovo, Motorola Mobility |
| R2-2101123 |
SCell states configuration in the same RRC message to activate/deactivate SCG |
Lenovo, Motorola Mobility |
| R2-2101235 |
Further Considerations on Efficient SCG Activation/Deactivation |
CATT |
| R2-2101312 |
On Support of Activation/Deactivation for SCG |
InterDigital |
| R2-2101464 |
Remaining open items on SCG deactivation feature |
Apple Inc |
| R2-2101481 |
UE behaviour on deactivated SCG |
Huawei, HiSilicon |
| R2-2101482 |
SCG activation and deactivation procedure |
Huawei, HiSilicon |
| R2-2101483 |
Selection of SCG activation state at mobility and resume |
Huawei, HiSilicon |
| R2-2101541 |
Consideration for some remaining FFSes |
Intel Corporation |
| R2-2101807 |
Discussion on SCG deactivation |
MediaTek Inc. |
| R2-2101865 |
LS RAN2 decisions for SCG deactivation |
Nokia, Nokia Shanghai Bell |
| R2-2101871 |
UE behaviour in SCG deactivated state |
Qualcomm Incorporated |
| R2-2101876 |
Further discussion for SCG deactivation |
SHARP Corporation |
| R2-2101883 |
Considerations on SCells in SCG deactivation |
CMCC |
| R2-2101884 |
Signallings of SCG activation and deactivation |
CMCC |
| R2-2101915 |
Further consideration on SCG activation and deactivation |
NTT DOCOMO INC. |
| R2-2101969 |
Summary of [AT113-e][230][eDCCA] Solution alternatives for SCG activation and deactivation (Huawei) |
Huawei |
| 8.2.3 |
Conditional PSCell change / addition |
|
| R2-2100292 |
Considerations on failure handling for CPAC |
China Telecommunication |
| R2-2100463 |
Discussion on the configuration of CPAC |
vivo |
| R2-2100464 |
Discussion on CPAC configuration scenarios |
vivo |
| R2-2100531 |
On Rel-17 Basic CPAC procedures |
Nokia, Nokia Shanghai Bell |
| R2-2100532 |
On Rel-17 Further CPAC functionalities |
Nokia, Nokia Shanghai Bell |
| R2-2100590 |
Progressing conditional configuration for R17 |
Samsung Telecommunications |
| R2-2100633 |
CPAC failure handling discussion |
Futurewei |
| R2-2100642 |
Candidate PSCell selection in CPAC |
NEC |
| R2-2100672 |
CPC configuration number restriction |
Spreadtrum Communications |
| R2-2100727 |
Support for CHO and CPAC coexistence |
LG Electronics |
| R2-2100728 |
Consideration on further enhancements in CPAC |
LG Electronics |
| R2-2100783 |
New timer for SDT failure detection |
LG Electronics |
| R2-2100827 |
SCG RLF handling in case CPC is configured |
ITRI |
| R2-2100847 |
Discussion on conditional PSCell addition |
OPPO |
| R2-2100848 |
Discussion on conditional PSCell change |
OPPO |
| R2-2100875 |
Details in conditional PSCell change and addition |
Apple |
| R2-2101124 |
Discussion on CPAC |
Lenovo, Motorola Mobility |
| R2-2101236 |
Further Discussion on CPAC |
CATT |
| R2-2101237 |
Introduction of CPA and Inter-SN CPC for 37 340 |
CATT |
| R2-2101238 |
Handling leftovers from email discussion [Post111-e][920] Conditional PSCell Change and Addition |
CATT |
| R2-2101270 |
Conditional PSCell Change / Addition |
Ericsson |
| R2-2101313 |
Coexistence of CHO and CPAC |
InterDigital, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
| R2-2101402 |
Introducing MR DC/CA further enhancements concerning CPAC |
Samsung Telecommunications |
| R2-2101403 |
Introducing MR DC/CA further enhancements concerning CPAC |
Samsung Telecommunications |
| R2-2101484 |
Conditional PSCell change/addition |
Huawei, HiSilicon |
| R2-2101566 |
Discussion on conditional PSCell addition and change |
ZTE Corporation, Sanechips |
| R2-2101567 |
Further consideration on conditional PSCell addition and change |
ZTE Corporation, Sanechips |
| R2-2101765 |
Discussion on CPAC Execution |
ETRI |
| R2-2101872 |
CPA and MN initiated Inter-SN CPC procedures: preparation and execution phases |
Qualcomm Incorporated |
| R2-2101875 |
SN initiated Inter-SN CPC procedure: preparation and execution phases |
Qualcomm Incorporated |
| R2-2101885 |
Considerations on CPAC |
CMCC |
| R2-2101886 |
Discussions about CPA and MN initiated inter-SN CPC procedures |
CMCC |
| R2-2101916 |
Further consideration on Conditional PSCel change and addition |
NTT DOCOMO INC. |
| R2-2101959 |
Coexistence of CHO and CPAC |
InterDigital, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, vivo |
| R2-2101970 |
Summary of [AT113-e][231][eDCCA] Solution alternatives for CPAC (CATT) |
CATT |
| R2-2102170 |
LS on Conditional PSCell Addition/Change agreements |
RAN2 |
| 8.3.1 |
Organizational, Requirements and Scope |
|
| R2-2100042 |
Reply LS on System support for Multi-USIM devices (R3-207207; contact: vivo) |
RAN3 |
| R2-2100471 |
Running CR to 36300 for Multi-USIM devices support |
vivo |
| R2-2100472 |
Running CR to 38300 for Multi-USIM devices support |
vivo |
| R2-2101632 |
Revised Work Plan for RAN Slicing |
CMCC |
| R2-2101633 |
Draft TR 38.832 v0.4.0 |
CMCC |
| R2-2101634 |
Report of [Post112-e][253][RAN slicing] Prioritized solutions for RAN slicing |
CMCC |
| R2-2101635 |
Draft TP for TR 38.832 v0.4.0 |
CMCC |
| R2-2102213 |
Running CR to 36300 for Multi-USIM devices support |
vivo |
| R2-2102214 |
Running CR to 36300 for Multi-USIM devices support |
vivo |
| 8.3.2 |
Paging collision avoidance |
|
| R2-2100244 |
Paging collision avoidance |
OPPO |
| R2-2100250 |
Multi-SIM Paging Collision Solution |
MITRE Corporation |
| R2-2100280 |
Further Consideration on Paging Collision Avoidance |
CATT |
| R2-2100428 |
Consideration on the Paging Collision |
ZTE Corporation, Sanechips |
| R2-2100434 |
Paging Collision Avoidance for Multi-RAT MUSIM UE |
Samsung |
| R2-2100445 |
Solutions for paging collisions |
Qualcomm Incorporated |
| R2-2100473 |
Evaluation on Paging Collision Solutions |
vivo |
| R2-2100507 |
RAN impacts of solutions for paging collision avoidance |
Nokia, Nokia Shanghai Bell |
| R2-2100724 |
Considerations for Paging Collision for Multi-SIM UEs |
Charter Communications, Inc |
| R2-2100732 |
Consideration on Options for Paging Collision |
LG Electronics |
| R2-2100849 |
Methods of MUSIM Page Collision Avoidance |
Apple |
| R2-2100900 |
Discussion on paging collision avoidance in Multi-SIM |
Sony |
| R2-2101097 |
On Paging Collision Avoidance |
Huawei, HiSilicon |
| R2-2101222 |
Definition and solution for paging collision, RRC Inactive, SI change |
Lenovo, Motorola Mobility |
| R2-2101296 |
Multi-SIM Paging Collision Solution |
MITRE Corporation |
| R2-2101304 |
Discussion of the paging collision problem |
Xiaomi Communications |
| R2-2101428 |
Paging collision avoidance |
Ericsson |
| R2-2101536 |
Multi-SIM Devices - Paging Collision |
MediaTek Inc. |
| R2-2101542 |
Support for SA2 agreed NAS based IMSI offset signaling in EPS |
Intel Corporation |
| R2-2101543 |
“Effective” solution for paging collision avoidance for 5GS |
Intel Corporation |
| R2-2101636 |
Discussion on SA2 LS, potential solutions and draft TP for slice-based cell (re)selection |
CMCC |
| R2-2101748 |
UE indication of paging collision for Multi-SIM |
ASUSTeK |
| 8.3.3 |
UE notification on network switching for multi-SIM |
|
| R2-2100245 |
UE notification on network switching for multi-SIM |
OPPO |
| R2-2100281 |
Further Consideration on Network Switching |
CATT |
| R2-2100290 |
Discussion of network switching for Multi-SIM |
China Telecommunication |
| R2-2100429 |
Consideration on the Switching Notification Procedure |
ZTE Corporation, Sanechips |
| R2-2100446 |
Network switching mechanisms for Multi-SIM |
Qualcomm Incorporated |
| R2-2100474 |
[post112-e][256][Multi-SIM] Network switching details (vivo) |
vivo |
| R2-2100475 |
Discussion on Switching Notification Procedure |
vivo |
| R2-2100482 |
Open issues on network switching scenarios |
Samsung Electronics Co., Ltd |
| R2-2100508 |
Switching notification procedure for basic switching scenarios for Single RX UE |
Nokia, Nokia Shanghai Bell |
| R2-2100509 |
On Additional scenarios for switching notification |
Nokia, Nokia Shanghai Bell |
| R2-2100654 |
Discussion on the transmission of busy indication |
Spreadtrum Communications |
| R2-2100725 |
Network Switching for Multi-SIM UEs |
Charter Communications, Inc |
| R2-2100731 |
Consideration on Scheduling gap for SIM Switching |
LG Electronics |
| R2-2100750 |
UE notification procedure for short time switching |
NEC |
| R2-2100763 |
Short-time and Long-time Switching Notification |
Sharp |
| R2-2100850 |
Methods of MUSIM Network Switching |
Apple |
| R2-2100851 |
Handling of BUSY indication in RRC INACTIVE state |
Apple |
| R2-2100901 |
Discussion on Busy Indication and Leaving in Multi-SIM |
Sony |
| R2-2101106 |
Switching Notification in MUSIM |
Lenovo, Motorola Mobility |
| R2-2101276 |
On coordinated switching from NW for MUSIM device |
Huawei, HiSilicon |
| R2-2101305 |
Discussion of the UE notification on network switching for multi-SIM |
Xiaomi Communications |
| R2-2101427 |
Graceful leaving for a MultiSIM device |
Ericsson |
| R2-2101537 |
Multi-SIM Devices - Notification upon Network Switching |
MediaTek Inc. |
| R2-2101544 |
Busy indication signaling for Multi-SIM |
Intel Corporation |
| R2-2101637 |
Solutions analysis and draft TP for slice-based RACH configuration |
CMCC |
| R2-2101749 |
MUSIM Release Assistance Info for network switching |
ASUSTeK |
| R2-2101780 |
Analysis on various scenarios of UE switching |
China Telecomunication Corp. |
| R2-2101789 |
Discussion on Scheduling gap for Periodic short-time switching |
China Telecomunication Corp. |
| R2-2101842 |
Consideration on Busy Indication |
LG Electronics Finland |
| R2-2101937 |
Considerations for MSIM UE notification on network switching |
Futurewei Technologies |
| R2-2101981 |
Summary of [AT113-e][242][NR][Multi-SIM] NAS vs. RRC signalling for paging collision and network switching (vivo) |
vivo |
| R2-2102262 |
[post112-e][256][Multi-SIM] Network switching details (vivo) |
vivo |
| 8.3.4 |
Paging with service indication |
|
| R2-2100200 |
Discussion on support of paging cause for Multi-SIM devices |
Samsung Electronics Co., Ltd |
| R2-2100246 |
Paging with service indication |
OPPO |
| R2-2100430 |
Consideration on the Paging Service Indication |
ZTE Corporation, Sanechips |
| R2-2100447 |
Service Type in Paging and Busy Indication |
Qualcomm Incorporated |
| R2-2100476 |
Discussion on Supporting of Paging Cause |
vivo |
| R2-2100655 |
Discussion on the transmission of paging cause |
Spreadtrum Communications |
| R2-2101098 |
Discussion on the paging with service indication |
Huawei, HiSilicon |
| R2-2101307 |
Discussion of the paging cause support for MUSIM |
Xiaomi Communications |
| R2-2101429 |
Introduction of a Paging cause indication |
Ericsson |
| R2-2101538 |
Multi-SIM Devices - Paging Cause |
MediaTek Inc. |
| 8.4.1 |
Organizational, Requirements and Scope |
|
| R2-2100038 |
LS on DAPS-like solution for service interruption reduction in Rel-17 IAB (R3-207184; contact: Samsung) |
RAN3 |
| R2-2100040 |
LS on CP-UP separation of Rel-17 IAB (R3-207198; contact: Samsung) |
RAN3 |
| R2-2100041 |
LS on inter-donor topology redundancy (R3-207199; contact: Samsung) |
RAN3 |
| R2-2100591 |
Updated workplan for Rel-17 IAB |
Qualcomm Incorporated (WI Rapporteur) |
| R2-2102288 |
Summary of [AT113-e][030][eIAB] Reply LS DAPS-like solution (Ericsson) |
Ericsson |
| R2-2102364 |
Reply LS on DAPS-like solution for service interruption reduction |
RAN2 |
| 8.4.2 |
Enhancements to improve topology-wide fairness, multi-hop latency and congestion mitigation |
|
| R2-2100225 |
Consideration on topology-wide fairness, multi-hop latency and congestion mitigation |
CATT |
| R2-2100358 |
Discussion on Topology-wide fairness, latency and flow control enhancement |
Intel Corporation |
| R2-2100477 |
Discussion on congestion, RLF and fairness handling |
vivo |
| R2-2100593 |
Simulations on fairness support in IAB topology |
Qualcomm Incorporated |
| R2-2100594 |
Enhancements to improve IAB multi-hop latency |
Qualcomm Incorporated |
| R2-2100708 |
IAB fairness scheduling |
NEC |
| R2-2100752 |
Discussion on the fairness enforcement and congestion mitigation for IAB |
Fujitsu |
| R2-2100753 |
Consideration on multi-hop latency in IAB |
Fujitsu |
| R2-2100801 |
Consideration of topology-wide fairness and multi-hop latency enhancements for eIAB |
Kyocera |
| R2-2100824 |
An elaboration of required PDB for multi-hop latency |
ITRI |
| R2-2100885 |
Solutions to ensure fairness, latency bounds and mitigation of congestion impacts in eIAB Networks |
Apple |
| R2-2100902 |
Topology-wide fairness and Latency enhancements and congestion mitigation |
Sony |
| R2-2101070 |
Enhancements for topology-wide fairness, multi-hop latency and congestion mitigation |
Huawei, HiSilicon |
| R2-2101086 |
Fairness, latency and congestion – solutions |
Samsung Electronics GmbH |
| R2-2101168 |
Report from email discussion [Post112-e][065][eIAB] Fairness Latency Congestion (Samsung) |
Samsung Electronics GmbH |
| R2-2101202 |
Hop-by-hop flow control in uplink |
Nokia, Nokia Shanghai Bell |
| R2-2101260 |
Multi-hop scheduling and local routing enhancements for IAB |
AT&T |
| R2-2101284 |
Enhancements to improve topology-wide fairness, multi-hop latency and congestion mitigation |
ZTE, Sanechips |
| R2-2101314 |
On multi-hop latency, fairness and congestion mitigation |
InterDigital |
| R2-2101448 |
On Topology-wide Fairness, Multi-hop Latency and Congestion Mitigation |
Ericsson |
| R2-2101502 |
Consideration on identified issues for fairness, latency and congestion |
LG Electronics |
| R2-2101820 |
Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation |
Futurewei Technologies |
| 8.4.3 |
Topology adaptation enhancements |
|
| R2-2100226 |
CHO and DAPS |
CATT |
| R2-2100227 |
RLF Indication and Local Rerouting |
CATT |
| R2-2100359 |
Discussion on Topology adaptation enhancements |
Intel Corporation |
| R2-2100360 |
Discussion on RAN3 LS of DAPS-like solution |
Intel Corporation |
| R2-2100478 |
On inter-CU Topology Adaptation Enhancements |
vivo |
| R2-2100592 |
Report from email discussion [Post112-e][066][eIAB] Topology Adaptation |
Qualcomm Incorporated |
| R2-2100595 |
Inter-donor-DU local rerouting for IAB |
Qualcomm Incorporated |
| R2-2100611 |
Re-routing enhancements in IAB |
Nokia, Nokia Shanghai Bell |
| R2-2100612 |
On CP_UP split for topology adapation enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2100754 |
Handling of descendant nodes and UEs in inter-CU CHO and RLF recovery |
Fujitsu |
| R2-2100802 |
Further consideration of topology adaptation enhancements for eIAB |
Kyocera |
| R2-2100886 |
Discussion on topology adaptation enhancements in eIAB Networks |
Apple |
| R2-2100903 |
Topology adaptation enhancements in IAB |
Sony |
| R2-2101071 |
Consideration of topology adaptation enhancement for R17-IAB |
Huawei, HiSilicon |
| R2-2101109 |
CHO in IAB system |
Lenovo, Motorola Mobility |
| R2-2101142 |
Discussion on IAB packet rerouting |
Lenovo, Motorola Mobility |
| R2-2101208 |
Discussion on RLF indication enhancement and local routing for R17-IAB |
CANON Research Centre France |
| R2-2101261 |
Topology adaptation enhancements for IAB |
AT&T |
| R2-2101282 |
Discussion on CP/UP separation |
ZTE, Sanechips |
| R2-2101283 |
Considerations on topology adaptation enhancements in IAB |
ZTE, Sanechips |
| R2-2101315 |
On IAB Topology Adaptation |
InterDigital |
| R2-2101449 |
On IAB Inter-donor Topology Adaptation |
Ericsson |
| R2-2101450 |
LS on DAPS-like solution for service interruption reduction |
Ericsson |
| R2-2101503 |
Consideration on local re-routing |
LG Electronics |
| R2-2101514 |
BH RLF indications with conditional mobility and local re-routing |
LG Electronics |
| R2-2101766 |
Discussion on Resource Reservation for CHO |
ETRI |
| R2-2101798 |
RAN2 impacts of Rel.17 IAB topology adaptation enhancements |
Futurewei Technologies |
| R2-2101905 |
Issues on UL RLF notification and CP-UP separation |
Samsung R&D Institute UK |
| R2-2102238 |
Report from email discussion [Post112-e][066][eIAB] Topology Adaptation |
Qualcomm Incorporated |
| 8.4.4 |
Duplexing enhancements, RAN2 scope |
|
| R2-2100479 |
Duplexing enhancements of inter-carrier DC |
vivo |
| R2-2101072 |
Duplexing enhancements for R17 IAB |
Huawei, HiSilicon |
| R2-2101100 |
Views on duplexing enhancements |
Samsung Electronics GmbH |
| R2-2101262 |
Duplexing enhancements for IAB |
AT&T |
| 8.5.1 |
Organizational |
|
| R2-2100043 |
Reply LS on Use of Survival Time for Deterministic Applications in 5GS (R3-207211; contact: Nokia) |
RAN3 |
| R2-2100066 |
LS on Clarification on URLLC QoS Monitoring (S2-2007825; contact: Huawei) |
SA2 |
| R2-2100715 |
Revised Rel-17 NR IIoT/URLLC Work Plan |
Nokia |
| 8.5.2 |
Enhancements for support of time synchronization |
|
| R2-2100215 |
Discussion on the time synchronisation enhancements |
Huawei, HiSilicon |
| R2-2100221 |
Discussion on Time Synchronization in Rel-17 |
CATT |
| R2-2100232 |
Propagation Delay Compensation Enhancements |
Ericsson |
| R2-2100267 |
Propagation Delay Compensation for TSN |
QUALCOMM Europe Inc. - Italy |
| R2-2100327 |
Further considerations on time synchronization and PDC |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2100417 |
Remaining aspect to support time synchronization |
Fujitsu |
| R2-2100425 |
Some considerations on propagation delay compensation |
China Telecom |
| R2-2100615 |
RAN Enhancements for Support of Timing Synchronization |
Intel Corporation |
| R2-2100716 |
Time Synchronization Signalling and Mobility Impact Analysis |
Nokia, Nokia Shanghai Bell |
| R2-2100781 |
Discussion on uplink time synchronization for TSN |
NTT DOCOMO, INC. |
| R2-2100829 |
Discussion on time sync maintenance during mobility |
vivo |
| R2-2100844 |
Consideration of TSN time synchronization in handover scenario |
OPPO |
| R2-2100941 |
Propagation Delay Compensation for TSN |
CANON Research Centre France |
| R2-2101119 |
Discussion on enabling UE side propagation delay compensation |
Lenovo, Motorola Mobility |
| R2-2101322 |
On propagation delay compensation |
MediaTek Inc. |
| R2-2101490 |
Mobility aspects of time synchronization |
Sequans Communications |
| R2-2101666 |
Propagation delay compensation and synchronization |
Samsung |
| R2-2101671 |
Mobility issue on time synchronization |
Beijing Xiaomi Mobile Software |
| R2-2101721 |
Enhancements for support of time synchronization for TSN |
CMCC |
| R2-2101809 |
Enhancements for support of time synchronization and PDC |
TCL Communication Ltd. |
| R2-2101862 |
Discussion on enhancements for support of time synchronization |
LG Electronics Inc. |
| R2-2102071 |
Summary on Enhancements for support of time synchronization (8.5.2) |
Ericsson |
| R2-2102266 |
Summary on Enhancements for support of time synchronization (8.5.2) |
Ericsson |
| R2-2102267 |
Summary on email discussion [AT113-e][507][IIoT] Summary of TSN (Ericsson) |
Ericsson |
| 8.5.3 |
Uplink enhancements for URLLC in unlicensed controlled environments |
|
| R2-2100214 |
Uplink enhancements for URLLC in UCE |
Huawei, HiSilicon |
| R2-2100222 |
Analysis on IIoT in Unlicensed Spectrum |
CATT |
| R2-2100233 |
Harmonizing UL CG enhancements in NR-U and URLLC |
Ericsson |
| R2-2100268 |
CG Harmonization for Unlicensed Controlled Environment |
QUALCOMM Europe Inc. - Italy |
| R2-2100717 |
Support of URLLC in Unlicensed Spectrum |
Nokia, Nokia Shanghai Bell |
| R2-2100758 |
Transmission Handling in UCE |
Sharp |
| R2-2100759 |
Autonomous transmission/Retransmission in Unlicensed Controlled Environments |
Sharp |
| R2-2100830 |
Simultaneous configuration of LCH based prioritization and CGRT |
vivo |
| R2-2100891 |
Consideration on URLLC over NR-U |
OPPO |
| R2-2100904 |
Considerations in unlicensed URLLC |
Sony |
| R2-2100905 |
Prioritization of UL transmissions in unlicensed URLLC |
Sony |
| R2-2100920 |
CG Harmonization for NR-U and IIoT/URLLC in Unlicensed Controlled Environments |
III |
| R2-2100921 |
Enhancements for URLLC in unlicensed controlled environments |
Lenovo, Motorola Mobility |
| R2-2101133 |
Enhancements for URLLC in unlicensed controlled environments |
Lenovo, Motorola Mobility |
| R2-2101321 |
Remaining issues on configured grant harmonization |
MediaTek Inc. |
| R2-2101508 |
IIoT operation in unlicensed controlled environments |
InterDigital |
| R2-2101520 |
IIOT CG operation on shared spectrum |
LG Electronics UK |
| R2-2101531 |
Considerations on UL Enhancement on the shared spectrum Channel |
ZTE Corporation, Sanechips |
| R2-2101614 |
Discussion on uplink enhancements for URLLC in unlicensed controlled environments |
CMCC |
| R2-2101667 |
LCH based Prioritization in UCE |
Samsung |
| R2-2101672 |
LBT failure and LCH based priority |
Beijing Xiaomi Mobile Software |
| R2-2101757 |
Uplink enhancements for URLLC in unlicensed controlled environments |
Intel Corporation |
| R2-2102072 |
Summary of URLLC over unlicensed controlled environment |
InterDigital |
| R2-2102073 |
Summary of URLLC over unlicensed controlled environment |
InterDigital |
| R2-2102087 |
Summary of URLLC over unlicensed controlled environment |
InterDigital |
| 8.5.4 |
RAN enhancements based on new QoS |
|
| R2-2100216 |
RAN enhancements based on new QoS related parameters |
Huawei, HiSilicon |
| R2-2100223 |
Discussion on Survival Time |
CATT |
| R2-2100234 |
RAN enhancements based on new QoS related parameters |
Ericsson |
| R2-2100269 |
RAN Enhancement to support new QoS |
QUALCOMM Europe Inc. - Italy |
| R2-2100328 |
Further considerations on new QoS |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2100418 |
Topics on new QoS handling |
Fujitsu |
| R2-2100449 |
Discussion on RAN enhancements based on Survival Time |
III |
| R2-2100614 |
Support for Survival Time and Burst Spread |
Intel Corporation |
| R2-2100718 |
Views on RAN Enhancement for New QoS Parameters |
Nokia, Nokia Shanghai Bell |
| R2-2100831 |
Disucussion on RAN enhancement to support survival time |
vivo |
| R2-2100856 |
Scheduling Assistance Information for support of new QoS |
Apple |
| R2-2100857 |
Reliability enhancements for CG/SPS |
Apple |
| R2-2100892 |
RAN enhancement based on new QoS |
OPPO |
| R2-2100922 |
Discussion on the support of survival time |
Lenovo, Motorola Mobility |
| R2-2101066 |
Open issues with survival time and proposal for way forward |
Samsung Electronics GmbH |
| R2-2101134 |
Discuss on the mechanism to guarantee the survival time |
Lenovo, Motorola Mobility |
| R2-2101509 |
Enhancements based on new QoS requirements |
InterDigital |
| R2-2101521 |
Implication of survival time |
LG Electronics UK |
| R2-2101615 |
Discussion on the support of new QoS parameters in RAN |
CMCC |
| R2-2101673 |
RAN impacts of the survival time |
Beijing Xiaomi Mobile Software |
| R2-2102074 |
Offline on RAN enhancements QoS [AT113-e][506] |
Nokia |
| R2-2102088 |
Reply LS on Sufficiency of Survival Time |
RAN2 |
| R2-2102229 |
RAN enhancement based on new QoS |
OPPO |
| R2-2102254 |
Summary of Agenda Item 8.5.4: RAN enhancements based on new QoS |
Nokia |
| 8.6.1 |
Organizational |
|
| R2-2100930 |
Report from email discussion [POST112-e][550][SDT] Further details of CG aspects |
Lenovo, Motorola Mobility |
| R2-2101162 |
Email discussion summary #551: Common aspects between CG and RACH |
ZTE Corporation, Sanechips |
| R2-2102075 |
Report of offline discussion on CBs and control plane issues [509] |
ZTE |
| R2-2102089 |
LS on small data transmissions in NR |
ZTE |
| R2-2102090 |
LS on uplink timing alignment for small data transmissions |
RAN2 |
| 8.6.2 |
User plane common aspects |
|
| R2-2100146 |
User Plane Common Aspects of RACH and CG based SDT |
Samsung Electronics Co., Ltd |
| R2-2100294 |
User plane common aspects of SDT |
CATT |
| R2-2100365 |
Common User plane aspects for SDT |
Intel Corporation |
| R2-2100419 |
Identified issue in [Post111-e][926]: CA and PDCP CA duplication |
Fujitsu |
| R2-2100749 |
Handling of new arriving data during SDT |
NEC |
| R2-2101136 |
The UP common issues for small data transmissions |
Lenovo, Motorola Mobility |
| R2-2101145 |
Handling of non-SDT DRB |
MediaTek Inc. |
| R2-2101160 |
User plane common aspects of SDT |
ZTE Corporation, Sanechips |
| R2-2101176 |
Common aspects for SDT |
Ericsson |
| R2-2101183 |
User plane common aspects for SDT |
Huawei, HiSilicon |
| R2-2101203 |
User Plane common aspects |
Nokia, Nokia Shanghai Bell |
| R2-2101221 |
Remaining issues on user plane aspects of NR small data transmission |
Qualcomm Incorporated |
| R2-2101370 |
Non-SDB handling during the SDT procedure |
Apple |
| R2-2101674 |
Collision between SDT and RACH |
Beijing Xiaomi Mobile Software |
| R2-2101750 |
Handling non-SDT data arrival during subsequent SDT |
ASUSTeK |
| R2-2102230 |
Handling of non-SDT DRB |
MediaTek |
| 8.6.3 |
Control plane common aspects |
|
| R2-2100139 |
Discussion on User Plane Aspect of Small Data Transmission |
vivo |
| R2-2100140 |
Duscussion on RRC-Controlled Small Data Transmission |
vivo |
| R2-2100147 |
Control Plane Common Aspects of RACH and CG based SDT |
Samsung Electronics Co., Ltd |
| R2-2100282 |
Discussion on SDT UP issues |
OPPO |
| R2-2100283 |
Discussion on SDT CP issues |
OPPO |
| R2-2100295 |
Considerations on control plane common aspects |
CATT |
| R2-2100366 |
Common Control plane aspects for SDT |
Intel Corporation |
| R2-2100668 |
Discussion on the general aspects for small data transmission |
Spreadtrum Communications |
| R2-2100764 |
Some open issues of SDT procedure |
Potevio Company Limited |
| R2-2100817 |
T319-like timer for the SDT procedure |
PANASONIC R&D Center Germany |
| R2-2100826 |
Discussion on how to handle cell reselection for the case of SDT |
ITRI |
| R2-2100906 |
Discussion on subsequent SDT in NR, and timer handling |
Sony |
| R2-2101112 |
Consideration on CP issues for small data transmission |
Lenovo, Motorola Mobility |
| R2-2101146 |
Subsequent Transmission of Small data in INACTIVE |
MediaTek Inc. |
| R2-2101161 |
Control plane common aspects of SDT |
ZTE Corporation, Sanechips |
| R2-2101177 |
CP aspects for SDT |
Ericsson |
| R2-2101184 |
Control plane common aspects for SDT |
Huawei, HiSilicon |
| R2-2101223 |
Remaining issues on control plane aspects of NR small data transmission |
Qualcomm Incorporated |
| R2-2101311 |
SDT control plane aspects |
Nokia, Nokia Shanghai Bell |
| R2-2101368 |
Subsequent data transmission for SDT |
Apple |
| R2-2101369 |
Control plane aspects on SDT procedure |
Apple |
| R2-2101407 |
RRC-less SDT |
NEC Telecom MODUS Ltd. |
| R2-2101507 |
Subsequent small data transmission |
InterDigital |
| R2-2101513 |
Subsequent data transmission and indication for non-SDT DRBs |
LG Electronics Inc. |
| R2-2101578 |
Small data transmission failure timer |
InterDigital, Asia Pacific Telecom, Ericsson, ETRI, FGI, Sharp, Sony |
| R2-2101619 |
SDT type selection and switch procedure |
CMCC |
| R2-2101675 |
Discussion on the RRC-less SDT |
Beijing Xiaomi Mobile Software |
| R2-2101867 |
Handling of the subsequent data |
ITL |
| R2-2101947 |
New timer for SDT failure detection |
LG Electronics Inc. |
| R2-2102086 |
Support of SRB transmission using SDT |
InterDigital, Intel Corporation, Huawei, HiSilicon, Lenovo, Motorola Mobility, Spreadtrum, OPPO, Nokia, Sony, ZTE corporation, Sanechips, Apple, Qualcomm |
| 8.6.4 |
Aspects specific to RACH based schemes |
|
| R2-2100141 |
Supporting Small Data Transmission via RA Procedure |
vivo |
| R2-2100148 |
Details of RACH bsaed Small Data Transmission |
Samsung Electronics Co., Ltd |
| R2-2100284 |
Discussion on RACH based SDT |
OPPO |
| R2-2100296 |
Considerations on transition into RRC_CONNECTED during subsequent SDT |
CATT |
| R2-2100367 |
Fallback, RACH resource partitioning and identification of SDT access |
Intel Corporation |
| R2-2100413 |
Fallback issue for 2-step RA based small data transmission |
SHARP Corporation |
| R2-2100669 |
Discussion on small data transmission for RACH-based scheme |
Spreadtrum Communications |
| R2-2100907 |
Discussion on context fetch and anchor relocation |
Sony |
| R2-2100908 |
Details of RA-based schemes for SDT in NR |
Sony |
| R2-2101137 |
Analysis on open issues of RA based SDT |
Lenovo, Motorola Mobility |
| R2-2101159 |
Consideration on RACH based small data transmission |
ZTE Corporation, Sanechips |
| R2-2101174 |
RACH configuration for SDT |
Ericsson |
| R2-2101204 |
Details on RACH specific schemes |
Nokia, Nokia Shanghai Bell |
| R2-2101214 |
Small data transmission with RA-based scheme |
Huawei, HiSilicon |
| R2-2101231 |
Discussion on RACH based NR small data transmission |
Qualcomm Incorporated |
| R2-2101505 |
RACH-based SDT precedure |
InterDigital |
| R2-2101620 |
Remaining issues on RACH based scheme |
CMCC |
| R2-2101621 |
Anchor relocation and context fetch |
CMCC |
| R2-2101751 |
Discussion on RO configuration between SDT and legacy RA |
ASUSTeK |
| 8.6.5 |
Aspects specific to CG based schemes |
|
| R2-2100142 |
Supporting Small Data Transmission via CG Configuration |
vivo |
| R2-2100145 |
Details of Configured Grant based Small Data Transmission |
Samsung Electronics Co., Ltd |
| R2-2100285 |
Discussion on CG based SDT |
OPPO |
| R2-2100297 |
Analysis on CG-based SDT |
CATT |
| R2-2100368 |
Handling of configured grant for SDT |
Intel Corporation |
| R2-2100420 |
Open issue in [Post112-e][550][STD]: PDCCH monitoring |
Fujitsu |
| R2-2100775 |
Discussion on beam operations for small data enhancements |
Google Inc. |
| R2-2100777 |
Discussion on CG-based small data transmission |
Google Inc. |
| R2-2100782 |
Separate BWP for Small Data Transmission |
LG Electronics |
| R2-2100784 |
CG Resource validity and MAC PDU rebuilding on SDT |
LG Electronics |
| R2-2100909 |
Details of CG-based scheme for SDT in NR |
Sony |
| R2-2101111 |
Consideration on CG based small data transmission |
Lenovo, Motorola Mobility |
| R2-2101138 |
Consideration on CG based small data transmission |
Lenovo, Motorola Mobility |
| R2-2101147 |
Aspects specific to CG based schemes |
Nokia, Nokia Shanghai Bell |
| R2-2101151 |
RRC-less SDT over CG |
MediaTek Inc. |
| R2-2101158 |
Configured grant based small data transmission |
ZTE Corporation, Sanechips |
| R2-2101175 |
Details of CG based SDT |
Ericsson |
| R2-2101213 |
Small data transmission with CG-based scheme |
Huawei, HiSilicon |
| R2-2101233 |
Discussion on CG based NR small data transmission |
Qualcomm Incorporated |
| R2-2101371 |
CG based SDT procedure |
Apple |
| R2-2101466 |
CG resource release for SDT |
ETRI |
| R2-2101506 |
CG-based SDT selection and configuration |
InterDigital |
| R2-2101622 |
Consideration on CG resource configuration |
CMCC |
| R2-2101676 |
Retransmission issue not included in the CG email discussion |
Beijing Xiaomi Mobile Software |
| R2-2101752 |
Beam selection for CG-SDT |
ASUSTeK |
| R2-2101753 |
Discussion on RNTI for CG-based SDT |
ASUSTeK |
| R2-2101835 |
Discussion on CG-SDT configuration |
Asia Pacific Telecom, FGI |
| R2-2101837 |
Beam operation for CG-SDT |
Asia Pacific Telecom, FGI |
| 8.7.1 |
Organizational |
|
| R2-2100070 |
Reply LS to Reply LS on Direct Discovery and Relay (S2-2009229; contact: OPPO) |
SA2 |
| R2-2100112 |
Work planning of R17 SL relay |
OPPO |
| R2-2100113 |
TR 38.836 V1.0.1 |
OPPO |
| R2-2100170 |
Removal of comparison section from TR38.836 for SL Relay |
MediaTek Inc., OPPO, Interdigital |
| R2-2100201 |
[Draft] LS on Direct Discovery and Relay |
CATT |
| R2-2101489 |
Comparison of L2 and L3 Relay Architectures |
Futurewei, Huawei, HiSilicon, MediaTek, Apple, Interdigital, Convida Wireless |
| 8.7.2.1 |
Layer 2 relay |
|
| R2-2100111 |
Left issues on L2 Relay |
OPPO |
| R2-2100124 |
Remaining issues on L2 U2N relay |
Qualcomm Incorporated |
| R2-2100125 |
Remaining issues on service continuity of L2 U2N relay |
Qualcomm Incorporated |
| R2-2100169 |
Evaluation and Conclusion for L2 UE-to-Network Relay and L2 UE-to-UE Relay |
MediaTek Inc., Apple, Interdigital, Futurewei, Huawei, Hisilicon, Convida |
| R2-2100202 |
Feasibility for Layer2 Relay |
CATT |
| R2-2100300 |
Discussion on remaining issues on L2 UE-to-Network Relay |
ZTE Corporation |
| R2-2100520 |
Remaining Control Plane Aspects for L2 Relays |
InterDigital |
| R2-2100521 |
Discussion on L2 Relay Architecture and QoS |
InterDigital |
| R2-2100535 |
Further discussions on L2 SL relay |
Ericsson |
| R2-2100656 |
Remaining issues for L2 relay |
Spreadtrum Communications |
| R2-2100867 |
Discussion on Layer 2 Solutions for UE-to-NW relay and UE-to-UE relay |
Apple |
| R2-2100910 |
Remaining issues on L2 relay |
Sony |
| R2-2101083 |
L3 vs L2 relaying |
Samsung Electronics GmbH |
| R2-2101107 |
Consideration on U2N relay and U2U relay |
Lenovo, Motorola Mobility |
| R2-2101179 |
Remaining issues on L2 U2N Relay |
vivo |
| R2-2101206 |
L3 vs L2 relaying |
Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2101300 |
Inter-gNB Path Switching for L2 U2N Relay |
Intel Corporation |
| R2-2101601 |
Open issues on L2 relay |
Xiaomi communications |
| R2-2101623 |
Remaining issue on RRC state for L2 relay |
CMCC |
| R2-2101754 |
Discussion on CP protocol stack for L2 U2U relay |
ASUSTeK |
| R2-2101768 |
RRC status transition reporting procedure |
LG Electronics Inc |
| R2-2101782 |
Clean-up of L2 sidelink relay |
Huawei, HiSilicon |
| R2-2102091 |
Summary document for AI 8.7.2.1 |
InterDigital |
| R2-2102098 |
TP on L2 Conclusion Section |
InterDigital |
| R2-2102110 |
Summary of [AT113-e][605][Relay] Continuation of L2 architecture issues (InterDigital) |
InterDigital |
| R2-2102116 |
TP on L2 Conclusion Section |
InterDigital |
| R2-2102223 |
Summary document for AI 8.7.2.1 |
InterDigital |
| R2-2102237 |
Summary document for AI 8.7.2.1 |
InterDigital |
| 8.7.2.2 |
Layer 3 relay |
|
| R2-2100110 |
Left issues on L3 Relay |
OPPO |
| R2-2100122 |
Remaining issues of L3 relay |
Qualcomm Incorporated |
| R2-2100203 |
Feasibility for Layer3 Relay |
CATT |
| R2-2100301 |
Consideration on QoS of L3 relay |
ZTE Corporation |
| R2-2100548 |
QoS for L3 UE-to-Network Relay |
Nokia, Nokia Shanghai Bell |
| R2-2100549 |
Path switching enhancement for L3 UE-to-Network relay |
Nokia, Nokia Shanghai Bell |
| R2-2101009 |
Remaining Open Issues for L3 Relay |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2101178 |
L3 SL Relay Architecture |
vivo |
| R2-2101781 |
Evaluation and conclusion for L3 sidelink relay |
Huawei, HiSilicon, MediaTek Inc., Interdigital, Apple, Futurewei, Convida Wireless, Spreadtrum Communications |
| R2-2102097 |
[AT113-e][606][Relay] TP on conclusions for L3 relay architecture |
Ericsson |
| R2-2102101 |
Summary of [AT113-e][606][Relay] Continuation of L3 architecture issues |
Ericsson |
| R2-2102115 |
[AT113-e][606][Relay] TP on conclusions for L3 relay architecture |
Ericsson |
| R2-2102221 |
Summary document for AI 8.7.2.2 |
Ericsson |
| R2-2102247 |
Summary document for AI 8.7.2.2 |
Ericsson |
| 8.7.3 |
Discovery model/procedure for sidelink relaying |
|
| R2-2100100 |
Remaining issues of Relay discovery and (re)selection |
OPPO |
| R2-2100126 |
Remaining issues on discovery and relay (re)selection |
Qualcomm Incorporated |
| R2-2100152 |
Proposal of items to be examined on discovery and relay (re-)selection for UE-to-UE relay in WI phase |
Mitsubishi Electric Co. |
| R2-2100204 |
Miscellaneouse Issues on Relay Discovery |
CATT |
| R2-2100308 |
Discussion on remaining issues for sidelink discovery |
ZTE Corporation |
| R2-2100522 |
Discovery Procedure for sidelink relay |
InterDigital |
| R2-2100533 |
Remaining aspects for discovery |
Ericsson |
| R2-2100534 |
Remaining aspects for relay (re)selection |
Ericsson |
| R2-2100624 |
On SL discovery for relaying |
Intel Corporation |
| R2-2100658 |
Discussion on remaining issues on relay discovery |
Spreadtrum Communications |
| R2-2100707 |
Relay reselection based on discovery |
Kyocera |
| R2-2100726 |
Relay discovery considerations |
Kyocera |
| R2-2100804 |
Discussion on sidelink relay discovery |
SHARP Corporation |
| R2-2100868 |
Discussion on remaining issues on relay discovery |
Apple |
| R2-2100924 |
Protocol stack for discovery message |
Samsung Electronics |
| R2-2100925 |
Clarification on AS layer differentiation for discovery message |
Samsung Electronics |
| R2-2100926 |
Discovery configuration for Remote UE out of coverage |
Samsung Electronics |
| R2-2101108 |
Relay Discovery in L2 and L3 relay case |
Lenovo, Motorola Mobility |
| R2-2101181 |
Remaining issues of sidelink relay discovery procedure |
vivo |
| R2-2101211 |
UE-to-Nwk Relay Discovery and (Re)selection for Path Switching in SL Relay |
Nokia, Nokia Shanghai Bell |
| R2-2101597 |
Discussion on relay discovery regarding non SL relay capable gNB |
Xiaomi communications |
| R2-2101624 |
Relay discovery and (re)selection |
CMCC |
| R2-2101783 |
Discussion on the discovery procedure |
Huawei, HiSilicon |
| R2-2102099 |
[AT113-e][607][Relay] Continuation of discovery open issues |
CATT |
| R2-2102111 |
TP of AI 8.7.3 |
CATT |
| R2-2102224 |
[AT113-e][607][Relay] Continuation of discovery open issues |
CATT |
| 8.7.4 |
Other |
|
| R2-2100109 |
Left issues on Scenario and L23 accessment |
OPPO |
| R2-2100123 |
Finalize the comparison and conclusion section of TR 38.836 |
Qualcomm Incorporated |
| R2-2100171 |
Discussion on Remote UEs in RRC Inactive |
MediaTek Inc. |
| R2-2100205 |
Further Clarification on the Sidelink Relay Scenario |
CATT |
| R2-2100309 |
Comparison of L2 and L3 Relay |
ZTE Corporation |
| R2-2100444 |
Remote UE connectivity |
MediaTek Inc. |
| R2-2100523 |
Relay selection and reselection |
InterDigital |
| R2-2100550 |
Open Issues on NR Sidelink Relaying |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100616 |
Conclusion on the feasibility of L2 and L3 based Sidelink Relaying |
Intel Corporation |
| R2-2100625 |
Further details on relay reselection |
Intel Corporation |
| R2-2100980 |
Comparative analysis of L2 and L3 SL Relay architecture |
Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R2-2101180 |
Consideration on Control Plane messages transmission path for remote UE |
vivo, Philips, Lenovo, Motorola Mobility, AT&T |
| R2-2101210 |
SI acquisition, CN Registration and RNAU |
Lenovo, Motorola Mobility |
| R2-2101325 |
Support of idle mode mobility for remote-UE in SL UE-to-Nwk relay |
Nokia, Nokia Shanghai Bell |
| R2-2101453 |
Providing Reliability and Coverage using Relays |
Lenovo, Motorola Mobility, Philips, AT&T, Fujitsu |
| R2-2101778 |
Further consideration of relay selection and reselection criteria |
LG Electronics Inc. |
| R2-2101784 |
Consideration on relay selection and reselection |
Huawei, HiSilicon |
| R2-2101785 |
Relay UE selection and reselection prioritization |
LG Electronics Inc. |
| R2-2101788 |
Relay reselection using discovery message and sidelink unicast link |
LG Electronics Inc. |
| R2-2101890 |
discussion on RRC procedures of L2 U2N relay |
ETRI |
| R2-2102060 |
Study on NR sidelink relay |
OPPO |
| R2-2102093 |
Summary document of AI 8.7.4 |
OPPO |
| R2-2102112 |
TP of AI 8.7.4 |
OPPO |
| R2-2102118 |
TP of AI 8.7.4 |
OPPO |
| R2-2102119 |
Summary document for AI 8.7.4 |
OPPO |
| R2-2102239 |
Summary document for AI 8.7.4 |
OPPO |
| R2-2102334 |
Summary of [AT113-e][015][NR16 V2X MOB DCCA] RRC II (OPPO) |
OPPO |
| 8.8.1 |
Organizational |
|
| R2-2100035 |
Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI (R3-207147; contact: Nokia) |
RAN3 |
| R2-2100048 |
Response to restricting the rate per UE per network slice (R3-207230; contact: ZTE) |
RAN3 |
| R2-2100050 |
Response to LS Reply on Enhancement of RAN Slicing (R3-207236; contact: CMCC, ZTE) |
RAN3 |
| R2-2100546 |
Discussion on slicing related reply LSs (R2-2008759 and R2-2010694) |
Nokia, Nokia Shanghai Bell |
| R2-2100766 |
Cell configuration within TA/RA to Support Allowed NSSAI |
LG Electronics UK |
| R2-2100893 |
Discussion on SA2 LS |
OPPO |
| R2-2101061 |
Considerations on scenarios and solution space of RAN slicing enhancements |
Lenovo, Motorola Mobility |
| R2-2101293 |
UE slice MBR enforcement in RAN |
Ericsson |
| R2-2101294 |
Network slice support in cells |
Ericsson |
| R2-2101487 |
Rel-15/16 Status of Cell Configuration on Network Slicing |
Futurewei |
| R2-2101488 |
DRAFT Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI |
Futurewei |
| R2-2101700 |
Discussion on the SA2 incoming LS on Cell Configuration within TA/RA to Support Allowed NSSAI |
Huawei, HiSilicon |
| R2-2101800 |
Revised Work Plan for RAN Slicing |
CMCC |
| R2-2101801 |
Draft TR 38.832 v040 |
CMCC |
| R2-2101802 |
Report of [Post112-e][253][RAN slicing] Prioritized solutions for RAN slicing |
CMCC |
| R2-2101803 |
Draft TP for TR 38.832 v040 |
CMCC |
| R2-2101933 |
Draft reply LS on Cell Configuration within TARA to Support Allowed NSSAI |
ZTE corporation, Sanechips |
| R2-2101973 |
Summary of [AT113-e][250][Slicing] LS replies to SA2 and RAN3 (NN) |
Nokia |
| R2-2102008 |
Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI |
RAN2 |
| R2-2102009 |
Reply LS on restricting the rate per UE per network slice |
RAN2 |
| R2-2102059 |
Study on enhancement of Radio Access Network (RAN) slicing |
CMCC |
| 8.8.2 |
Slice based cell reselection under network control |
|
| R2-2100128 |
Discussion on candidate solutions of slice-based cell (re)selection |
Qualcomm Incorporated |
| R2-2100249 |
5G RAN Slicing Framework During Cell Selection / Reselection Phases |
MITRE Corporation |
| R2-2100362 |
Different slice availability in registration area |
Intel Corporation |
| R2-2100489 |
Cell (re)selection based on preferred frequency(s) per slice |
Beijing Xiaomi Software Tech |
| R2-2100547 |
Discussion on cell selection and reselection for slicing |
Nokia, Nokia Shanghai Bell |
| R2-2100646 |
Considerations on contents of slice related cell selection info |
KDDI Corporation |
| R2-2100660 |
Discussion on the awareness of intended slice for MT service |
Spreadtrum Communications |
| R2-2100661 |
Discussion on slice based cell (re)selection |
Spreadtrum Communications |
| R2-2100704 |
Remaining issues on slice-based (re)-selection |
vivo |
| R2-2100762 |
Discussion on slice based cell selection and reselection |
China Telecommunications |
| R2-2100767 |
Broadcast information for slice aware cell selection/cell reselection |
LG Electronics UK |
| R2-2100768 |
Further discussion on intended slices |
LG Electronics UK |
| R2-2100876 |
Discussion on slice based cell selection and re-selection |
Apple |
| R2-2100877 |
RAN slicing in shared network |
Apple |
| R2-2100894 |
Consideration on slice-specific cell (re)selection |
OPPO |
| R2-2100927 |
Clarification for slice related cell selection info in SIB |
Samsung Electronics |
| R2-2100928 |
Slice related cell reselection info in RRCRelease |
Samsung Electronics |
| R2-2100964 |
Slice based Cell Reselection under Network Control |
CATT |
| R2-2101194 |
Consideration on slice specific cell selection and reselection |
ZTE corporation, Sanechips |
| R2-2101212 |
Access to an Intended Slice |
Lenovo, Motorola Mobility |
| R2-2101295 |
TP: Solution 1 and 2 for fast access to slice |
Ericsson |
| R2-2101394 |
Slice-specific system information for cell selection and reselection |
Google Inc. |
| R2-2101699 |
Slice based Cell (re)selection under network control |
Huawei, HiSilicon |
| R2-2101804 |
Discussion on SA2 LS, potential solutions and draft TP for slice-based cell (re)selection |
CMCC |
| R2-2101974 |
Summary of [AT113-e][251][Slicing] Conclusions on slice-based cell (re)selection (Huawei) |
Huawei |
| R2-2102231 |
Considerations on contents of slice related cell selection info |
KDDI Corporation |
| 8.8.3 |
Slice based RACH configuration or access barring |
|
| R2-2100129 |
Discussion on candidate solutions of slice-based RACH |
Qualcomm Incorporated |
| R2-2100363 |
Consideration of slice based RACH |
Intel Corporation |
| R2-2100424 |
Considerations on the solutions of slice based RACH configuration |
Beijing Xiaomi Software Tech |
| R2-2100599 |
RACH prioritisation for slices |
Nokia, Nokia Shanghai Bell |
| R2-2100662 |
Consideration on slice based RACH configuration |
Spreadtrum Communications |
| R2-2100705 |
Remaining issues on RACH configuration |
vivo |
| R2-2100878 |
Discussion on slice based RACH and cell barring |
Apple |
| R2-2100895 |
Consideration on slice-specific RACH |
OPPO |
| R2-2100929 |
Consideration on slice-specific separate RACH resources pool |
Samsung Electronics |
| R2-2101062 |
Considerations on solutions for slice-specific RACH configuration |
Lenovo, Motorola Mobility |
| R2-2101195 |
Consideration on the slice specific RACH configuration |
ZTE corporation, Sanechips |
| R2-2101405 |
RSRP Thresholds for RACH separation and prioritisation for numerous slice configurations |
NEC Telecom MODUS Ltd. |
| R2-2101701 |
Slice based RACH configuration |
Huawei, HiSilicon |
| R2-2101805 |
Solutions analysis and draft TP for slice-based RACH configuration |
CMCC |
| R2-2101975 |
Summary of [AT113-e][252][Slicing] Conclusions on slice-based RACH configuration (CMCC) |
CMCC |
| 8.9.1 |
Organizational, Scope and Requirements |
|
| R2-2100029 |
LS on Paging Enhancement (R1-2009801; contact: MediaTek) |
RAN1 |
| R2-2100030 |
LS on signalling method for TRS/CSI-RS occasion(s) for idle/inactive UE(s) (R1-2009848; contact: Samsung) |
RAN1 |
| 8.9.2 |
Idle/inactive-mode UE power saving |
|
| R2-2100143 |
Paging Enhancements_UE Grouping |
Samsung Electronics Co., Ltd |
| R2-2100144 |
Paging Enhancements_DRX cycle for monitoring paging |
Samsung Electronics Co., Ltd |
| R2-2100153 |
Discussion on paging enhancement for power saving |
OPPO |
| R2-2100298 |
Considerations on UE grouping mechanism with Paging Enhancement |
CATT |
| R2-2100313 |
Power saving enhancements for paging reception |
Qualcomm Incorporated |
| R2-2100389 |
Report of [POST112-e][064][Pow17] Group Determination (Intel) |
Intel Corporation |
| R2-2100390 |
Discussion on paging enhancement |
Xiaomi Communications |
| R2-2100457 |
Paging enhancement in idle inactive mo de f or p owe r sa ving |
vivo |
| R2-2100458 |
RAN2 impacts on TRS/CSI-RS in idle inactive mode |
vivo |
| R2-2100682 |
Paging Enhancements for UE Power Savings |
Convida Wireless |
| R2-2100852 |
NR UE Power Save Paging IDLE/INACTIVE UE Grouping Schemes |
Apple |
| R2-2100911 |
Discussion on enhancements for idle/inactive-mode UE power saving |
Sony |
| R2-2100993 |
UE subgrouping for paging enhancement |
LG Electronics Inc. |
| R2-2100994 |
draft LS on Paging Enhancement for UE power saving |
LG Electronics Inc. |
| R2-2101115 |
Consideration on Idle/inactive-mode UE power saving |
Lenovo, Motorola Mobility |
| R2-2101148 |
Detail on paging sub-grouping indication and determination |
Nokia, Nokia Shanghai Bell |
| R2-2101274 |
Paging enhancements for idle/inactive mode UE |
Huawei, HiSilicon |
| R2-2101301 |
Network assigned subgrouping |
Intel Corporation |
| R2-2101539 |
UE-Group Paging Early Indication |
MediaTek Inc. |
| R2-2101738 |
Paging enhancements |
Ericsson |
| R2-2101841 |
Paging Enhancements for Power Saving |
Asia Pacific Telecom, FGI |
| R2-2101887 |
Considerations on UE paging enhancement |
CMCC |
| R2-2101895 |
Further discussion on UE grouping |
ZTE corporation, Sanechips |
| 8.9.3 |
Other aspects, RAN2 impacts |
|
| R2-2100154 |
Discussion on signaling aspects of TRS/CSI-RS occasion(s) for idle/inactive Ues |
OPPO |
| R2-2100299 |
Considerations on configuration of TRS/CSI-RS |
CATT |
| R2-2100345 |
Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE |
Xiaomi Communications |
| R2-2100816 |
TRS/CSI-RS for idle and inactive mode UE |
SHARP Corporation |
| R2-2100853 |
NR UE Power Save TRS/CSI-RS Signaling for IDLE/INACTIVE UEs |
Apple |
| R2-2100912 |
Discussion on TRS/CSI-RS configuration of idle/inactive-mode UEs |
Sony |
| R2-2101275 |
On potential TRS/CSI-RS for idle/inactive mode UE |
Huawei, HiSilicon |
| R2-2101302 |
TRS/CSI-RS configuration and availability for idle/inactive-mode UE |
Intel Corporation |
| R2-2101310 |
Potential TRS/CSI-RS occasion(s) |
Nokia, Nokia Shanghai Bell |
| R2-2101739 |
TRS/CSI-RS exposure |
Ericsson |
| R2-2101888 |
Considerations on TRS CSI-RS occasion(s) for idle inactive UE(s) |
CMCC |
| R2-2102387 |
Summary of [041][ePowSav] TRS/CSI-RS for IDLE INACTIVE |
Xiaomi Communications (email discussion rapporteur) |
| R2-2102439 |
Summary of [041][ePowSav] TRS/CSI-RS for IDLE INACTIVE |
Xiaomi Communications (email discussion rapporteur) |
| R2-2102469 |
Summary of [041][ePowSav] TRS/CSI-RS for IDLE INACTIVE |
Xiaomi Communications (email discussion rapporteur) |
| 8.10 |
NR Non-Terrestrial Networks (NTN) |
|
| R2-2100229 |
Stage 2 Running CR 38.300 NR-NTN |
THALES |
| 8.10.1 |
Organizational |
|
| R2-2100033 |
Reply LS on LS on signalling of satellite backhaul connection (R3-207060; contact: Huawei) |
RAN3 |
| R2-2100067 |
AN-PDB and PER targets for satellite access (S2-2009225; contact: Quacomm) |
SA2 |
| R2-2100330 |
Discussion on geographical fixed CGI |
CATT |
| R2-2100331 |
[Draft] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G |
CATT |
| R2-2100529 |
On Cell Identifier for NTN |
Nokia, Nokia Shanghai Bell |
| R2-2100540 |
Stage-3 running RRC CR for NTN Rel-17 |
Ericsson |
| R2-2100582 |
NR-NTN: Cell ID Handling |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100746 |
[Draft] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G |
Qualcomm Incorporated |
| R2-2100747 |
[Draft] Reply LS on AN-PDB and PER targets for satellite access |
Qualcomm Incorporated |
| R2-2101198 |
Running CR to 38.304 for NTN |
ZTE corporation, Sanechips |
| R2-2101199 |
Understanding on the AN-PDB and PER targets for satellite access |
ZTE corporation, Sanechips |
| R2-2101200 |
Draft reply LS on the AN-PDB and PER targets for satellite access |
ZTE corporation, Sanechips |
| R2-2101277 |
[DRAFT] Reply LS on SA WG2 assumptions AN-PDB and PER targets for satellite access |
THALES |
| R2-2101577 |
Stage 3 running CR 38.321 |
InterDigital |
| R2-2101608 |
Discussion on RAN3 LS about architecture aspects for using satellite access in 5G |
CMCC |
| R2-2102012 |
[AT113-e][102][NTN] Reply LSs to SA2 and RAN3 |
Qualcomm Incorporated |
| R2-2102041 |
[Draft] Reply LS on AN-PDB and PER targets for satellite access |
Qualcomm Incorporated |
| R2-2102042 |
[Draft] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G |
Qualcomm Incorporated |
| R2-2102049 |
Stage 2 Running CR 38.300 NR-NTN |
THALES |
| R2-2102050 |
Stage-3 running RRC CR for NTN Rel-17 |
Ericsson |
| R2-2102051 |
Running CR to 38.304 for NTN |
ZTE corporation, Sanechips |
| R2-2102052 |
Stage 3 running CR 38.321 |
InterDigital |
| R2-2102053 |
Reply LS on AN-PDB and PER targets for satellite access |
RAN2 |
| R2-2102054 |
Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G |
RAN2 |
| R2-2102057 |
RAN3 feedback on worksplit between RAN2 Running CR and RAN3 BL CR |
THALES |
| R2-2102252 |
Support Non-Terrestrial Networks |
Thales (Moderator) |
| R2-2102497 |
Reply LS on AN-PDB and PER targets for satellite access |
RAN2 |
| R2-2102498 |
Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G |
RAN2 |
| 8.10.2 |
User Plane |
|
| R2-2101576 |
MAC open issues |
InterDigital |
| 8.10.2.1 |
RACH aspects |
|
| R2-2100158 |
Discussion on RACH in NTN |
OPPO |
| R2-2100178 |
TA related issues |
Beijing Xiaomi Mobile Software |
| R2-2100251 |
RACH Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100332 |
Discussion on HARQ Aspects in NTN |
CATT |
| R2-2100333 |
Discussion on left issues of RACH in NR NTN |
CATT |
| R2-2100379 |
Pre-compensation for NTN |
Intel Corporation |
| R2-2100415 |
Considerations on RACH procedure enhancements in NTN |
CAICT |
| R2-2100663 |
Discussion on Random Access in NTN |
Spreadtrum Communications |
| R2-2100740 |
Details of the start offset in Random Access procedure |
Qualcomm Incorporated |
| R2-2100828 |
Discussion on NTN TA pre-compensation |
ITRI |
| R2-2100884 |
On Preamble Ambiguity in Non Terrestrial Networks |
Apple |
| R2-2100998 |
Remaining issues on RACH in NTN |
Huawei, HiSilicon |
| R2-2101048 |
Discussion on 2-Step RACH adaptation in NTN |
Nokia, Nokia Shanghai Bell |
| R2-2101125 |
Considerations on RA type selection and switching in NTN |
Lenovo, Motorola Mobility |
| R2-2101126 |
Preamble ambiguity for UE without TA pre-compensation capability |
Lenovo, Motorola Mobility |
| R2-2101404 |
Support of UEs with different pre-compensation capabilities |
NEC Telecom MODUS Ltd. |
| R2-2101494 |
On Random Access in NTNs |
Ericsson |
| R2-2101575 |
RACH aspects |
InterDigital |
| R2-2101582 |
Discussion on random access aspects |
LG Electronics Inc. |
| R2-2101584 |
Considerations on Random Access in NTN |
ZTE Corporation, Sanechips |
| R2-2101790 |
NTN 2-step RACH selection enhancements |
Convida Wireless |
| R2-2101823 |
UE calculated TA report |
Asia Pacific Telecom, FGI |
| R2-2101833 |
Enhancements on RACH in NTN |
Asia Pacific Telecom, FGI |
| 8.10.2.2 |
Other MAC aspects |
|
| R2-2100159 |
Discussion on MAC timers in NTN |
OPPO |
| R2-2100160 |
HARQ impact on DRX and LCP in NTN |
OPPO |
| R2-2100161 |
Report of [Post112-e][152][NTN] UL scheduling enhancements |
OPPO |
| R2-2100179 |
HARQ related issues |
Beijing Xiaomi Mobile Software |
| R2-2100252 |
Miscellaneous MAC Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100261 |
On Disabling uplink HARQ retransmission and Associated LCP Impacts |
MediaTek Inc. |
| R2-2100262 |
Round trip delay offset for configured grant timers |
MediaTek Inc. |
| R2-2100334 |
Discussion on UL Scheduling Enhancements in NR NTN |
CATT |
| R2-2100381 |
HARQ issues for NTN |
Intel Corporation |
| R2-2100416 |
Considerations on MAC timers in NTN |
CAICT |
| R2-2100664 |
Discussion on HARQ and related timers |
Spreadtrum Communications |
| R2-2100741 |
Support of disabling UL HARQ retransmission |
Qualcomm Incorporated |
| R2-2100881 |
On User Plane Latency Reduction Mechanisms in Non Terrestrial Networks |
Apple |
| R2-2100914 |
Other MAC enhancements in NTN |
Sony |
| R2-2100999 |
Further consideration on HARQ and LCP in NTN |
Huawei, HiSilicon |
| R2-2101057 |
Discussion on HARQ uplink retransmission signalling in NTN |
Nokia, Nokia Shanghai Bell |
| R2-2101063 |
On UL scheduling enhancements and UE-calculated TA report in NTN |
Nokia, Nokia Shanghai Bell |
| R2-2101067 |
Discussion on DRX operation associated with blind retransmission |
PANASONIC R&D Center Germany |
| R2-2101118 |
Discussion on DRX for NTN |
Lenovo, Motorola Mobility |
| R2-2101254 |
Enhancements on UL scheduling for NTN |
THALES |
| R2-2101297 |
Enhancements for NTN on MAC Layer |
THALES |
| R2-2101493 |
On scheduling, HARQ, and DRX for NTNs |
Ericsson |
| R2-2101573 |
HARQ timer aspects |
InterDigital |
| R2-2101580 |
Discussion on scheduling enhancement |
LG Electronics Inc. |
| R2-2101583 |
Discussion on disabling HARQ feedback and uplink retransmission |
LG Electronics Inc. |
| R2-2101585 |
Considerations on HARQ in NTN |
ZTE Corporation, Sanechips |
| R2-2101716 |
Outstanding Left-Issues for HARQ operation in NTN |
CMCC |
| R2-2101814 |
UE calculated TA report |
Asia Pacific Telecom co. Ltd |
| R2-2102013 |
Summary of offline 103 - [NTN] HARQ aspects |
InterDigital |
| R2-2102043 |
Summary of offline 103 - [NTN] HARQ aspects |
InterDigital |
| 8.10.2.3 |
RLC and PDCP aspects |
|
| R2-2100253 |
RLC and PDCP Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100357 |
Remaining Issues in RLC/PDCP Aspects of NR-NTN |
MediaTek Inc. |
| R2-2101259 |
Remaining Aspects on Enhancements for NTN on RLC and PDCP Timers |
THALES |
| R2-2101492 |
On RLC and PDCP for NTNs |
Ericsson |
| R2-2101518 |
On RLC t-Reassembly for NTN |
Sequans Communications |
| R2-2101532 |
Additional PDCP aspects for NTN |
Sequans Communications |
| 8.10.3 |
Control Plane |
|
| R2-2100883 |
Considerations on ephemeris database and parameter distribution to UEs in Non Terrestrial Networks |
Apple |
| 8.10.3.1 |
Earth fixed/moving beams related issues |
|
| R2-2100162 |
Discussion on feeder link switch’s impact on mobility procedure |
OPPO |
| R2-2100259 |
Improving Tracking Area Updates in NR-NTN |
MediaTek Inc. |
| R2-2100380 |
Feeder link switch over NTN |
Intel Corporation |
| R2-2100528 |
On Feeder Link Mobility in Transparent Satellite Payload Scenarios |
Nokia, Nokia Shanghai Bell |
| R2-2100578 |
Beam type-related information of LEO satellites |
LG Electronics Inc. |
| R2-2100666 |
Discussion on Floor Layout Information |
Spreadtrum Communications |
| R2-2100742 |
TAC update procedure |
Qualcomm Incorporated |
| R2-2100811 |
Enhancements on cell reselection for earth moving and fixed beams |
Xiaomi |
| R2-2100820 |
Fixed Tracking Area and the Tracking Area Code in NTN |
PANASONIC R&D Center Germany |
| R2-2101406 |
TAI update for earth moving cell |
NEC Telecom MODUS Ltd. |
| R2-2101574 |
Mobility enhancements for feeder-link switch |
InterDigital |
| R2-2101607 |
Considerations on Soft TAI Update |
CMCC |
| R2-2102014 |
Summary of offline 104 - [NTN] TAC update |
CMCC |
| R2-2102044 |
Summary of offline 104 - [NTN] TAC update |
CMCC |
| 8.10.3.2 |
Idle/Inactive mode |
|
| R2-2100163 |
Discussion on idle/inactive mode procedures in NTN |
OPPO |
| R2-2100254 |
Idle and Inactive Mode Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100260 |
On Cell Re-selection in NR-NTN |
MediaTek Inc. |
| R2-2100291 |
The design of satellite ephemeris in NTN |
China Telecommunication |
| R2-2100335 |
Further Discussion on the IDLE and Inactive Mode for NTN |
CATT |
| R2-2100347 |
Idle mode aspects for NTN |
Ericsson |
| R2-2100382 |
Idle mode operation in NTN |
Intel Corporation |
| R2-2100527 |
Report from [Post112-e][153][NTN] Idle mode aspects (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2100579 |
Contents of ephemeris information and remaining iissues |
LG Electronics Inc. |
| R2-2100809 |
Control plane for idle mode UE |
Xiaomi |
| R2-2100880 |
Cell Selection And Cell Reselection Solutions for Non Terrestrial Networks |
Apple, BT Plc. |
| R2-2100913 |
Idle mode enhancement in NTN |
Sony |
| R2-2101000 |
Discussion on cell reselection in NTN |
Huawei, HiSilicon |
| R2-2101127 |
Ephemeris provisioning for satellite and HAP constellation |
Lenovo, Motorola Mobility |
| R2-2101196 |
Discussion on cell selection and reselection in NTN |
ZTE corporation, Sanechips |
| R2-2101201 |
Understanding on the newly introduced Access Technology identifier for NTN |
ZTE corporation, Sanechips |
| R2-2101572 |
Cell reselection in NTN |
InterDigital |
| R2-2101609 |
Discussion of cell selection/reselection and ephemeris in NTN |
CMCC |
| R2-2101707 |
Considerations on satellite ephemeris |
Huawei, HiSilicon |
| R2-2101755 |
PLMN separation for NTN & TN |
ASUSTeK |
| R2-2101779 |
NTN Indication and Idle mode enhancements |
Convida Wireless |
| R2-2101786 |
NTN cell selection and Idle mode enhancements |
Convida Wireless |
| R2-2101787 |
NTN cell reselection and Idle mode enhancements |
Convida Wireless |
| R2-2101924 |
Discussion of cell selection/reselection and ephemeris in NTN |
CMCC |
| R2-2102015 |
Summary of offline 105 - [NTN] Idle mode aspects |
Nokia |
| 8.10.3.3 |
Connected mode |
|
| R2-2100164 |
Discussion on mobility management for connected mode UE in NTN |
OPPO |
| R2-2100255 |
Connected Mode Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100258 |
Efficient Configuration of SMTC and Measurement Gaps in NR-NTN |
MediaTek Inc. |
| R2-2100336 |
Consider on measurement in NTN system |
CATT |
| R2-2100346 |
Connected mode aspects for NTN |
Ericsson |
| R2-2100383 |
Location based measurement event and location based CHO execution condition for NTN |
Intel Corporation |
| R2-2100384 |
Measurement framework to support NTN |
Intel Corporation |
| R2-2100530 |
On SMTC and measurement gaps for NTN |
Nokia, Nokia Shanghai Bell |
| R2-2100580 |
Further considerations on CHO, location reporting, and measurement window in NTN |
LG Electronics Inc. |
| R2-2100665 |
Discussion on Mobility in NTN |
Spreadtrum Communications |
| R2-2100744 |
Configuration and execution of CHO |
Qualcomm Incorporated |
| R2-2100745 |
SMTC and measurement gap configuration |
Qualcomm Incorporated |
| R2-2100806 |
Discussion on mobility management in NTN |
Xiaomi |
| R2-2100822 |
Overhead Reduction for the Handover Procedure in NTN |
PANASONIC R&D Center Germany |
| R2-2100882 |
Analysis of Proposed Conditional Handover Solutions for Non Terrestrial Networks |
Apple |
| R2-2100915 |
Mobility management in NTN |
Sony |
| R2-2100992 |
Measurement window enhancements for NTN cell |
LG Electronics Inc. |
| R2-2101110 |
Conditional handover in NTN system |
Lenovo, Motorola Mobility |
| R2-2101128 |
Considerations on measurements in NTN |
Lenovo, Motorola Mobility |
| R2-2101129 |
CHO in NTN system |
Lenovo, Motorola Mobility |
| R2-2101197 |
Discussion on time(r) and location CHO triggering event configuration in NTN |
ZTE corporation, Sanechips |
| R2-2101298 |
Service continuity between NTN and TN |
HUGHES Network Systems, Thales, BT Plc, Turkcell, Vodafone, ESA |
| R2-2101547 |
Further considerations on CHO, location reporting, and measurement window in NTN |
LG Electronics Inc. |
| R2-2101610 |
Discussion of service continuity between Non-Terrestrial Network and Terrestrial Network |
CMCC |
| R2-2101611 |
Further discussion of mobility enhancements for NTN |
CMCC |
| R2-2101708 |
Discussion on CHO in NTN |
Huawei, HiSilicon |
| R2-2101709 |
Discussion on location based measurement in NTN |
Huawei, HiSilicon |
| R2-2101792 |
NTN ANR enhancements |
Convida Wireless |
| R2-2101859 |
SMTC and measurement gap configuration in NTN |
Rakuten Mobile, Inc |
| R2-2102016 |
Summary of offline 106 - [NTN] CHO aspects |
Ericsson |
| R2-2102045 |
Summary of offline 106 - [NTN] CHO aspects |
Ericsson |
| 8.10.3.4 |
LCS aspects |
|
| R2-2100256 |
LCS Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2100337 |
Discussion on LCS request and response enhancement in NTN |
CATT |
| R2-2100348 |
NTN location reporting and network identifiers |
Ericsson |
| R2-2100743 |
Discussion on RAN3 LS on UE positioning |
Qualcomm Incorporated |
| R2-2100810 |
Discussion on location service for NTN |
Xiaomi |
| R2-2101069 |
UE Positioning Methods in NR-NTN |
THALES |
| R2-2101150 |
Summary of [Post112-e][151][NTN] LCS for NTN (Fraunhofer) |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2102034 |
Possible questions to SA3-LI & SA3 on LCS in NTN |
Thales, Vodafone, Fraunhofer IIS, Fraunhofer HHI |
| R2-2102035 |
Possible questions to SA3-LI & SA3 on LCS in NTN |
Thales, Vodafone, Fraunhofer IIS, Fraunhofer HHI, Turkcell, BT |
| R2-2102036 |
[DRAFT] LS about location requirements for NTN |
Thales |
| R2-2102055 |
LS about location requirements for NTN |
RAN2 |
| 8.11.1 |
Organizational |
|
| R2-2100649 |
Consideration on R17 positioning WI Scope |
Intel Corporation |
| R2-2101387 |
draft LS to capture Text Proposal for TR 38.857 |
Ericsson |
| R2-2101388 |
Report on TR 38.857 |
Ericsson |
| R2-2102103 |
draft LS to capture Text Proposal for TR 38.857 |
Ericsson |
| R2-2102114 |
LS to capture Text Proposal for TR 38.857 |
RAN2 |
| R2-2102122 |
draft LS to capture Text Proposal for TR 38.857 |
Ericsson |
| R2-2102125 |
LS to capture Text Proposal for TR 38.857 |
RAN2 |
| R2-2102277 |
Reply LS on Latency of NR Positioning Protocols (R3-211121; contact: Ericsson) |
RAN3 |
| 8.11.2.1 |
Latency analysis and latency enhancements |
|
| R2-2100373 |
Discussion on Enhancements for Latency Reduction |
InterDigital, Inc. |
| R2-2100407 |
Summary of [Post112-e][617][POS] Evaluation of latency enhancement solutions (CATT) |
CATT |
| R2-2100648 |
Report of [Post112-e][616][POS] TP for latency analysis results (Intel) |
Intel Corporation |
| R2-2100653 |
TP of [Post112-e][616][POS] TP for latency analysis results (Intel) |
Intel Corporation |
| R2-2100683 |
Discussion on A-PRS and semi-persistent PRS |
vivo |
| R2-2100685 |
Discussion on latency enhancement for R17 positioning |
vivo |
| R2-2100814 |
Positioning enhancements on latency reduction |
Xiaomi |
| R2-2100869 |
Discussion on latency reduction for NR positioning enhancements |
Apple |
| R2-2100933 |
On Positioning Latency Reduction Solutions |
Lenovo, Motorola Mobility |
| R2-2101227 |
Discussion on positioning latency |
Huawei, HiSilicon |
| R2-2101392 |
Discussion on Latency Aspects |
Ericsson |
| R2-2101469 |
Positioning Latency Reduction |
Qualcomm Incorporated |
| R2-2101870 |
Discussion on latency reduction solutions |
Nokia, Nokia Shanghai Bell |
| R2-2101906 |
Latency reduction via configured grant for positioning |
Samsung R&D Institute UK |
| R2-2101907 |
Latency reduction via measurement gap signalling optimization |
Samsung R&D Institute UK |
| R2-2101921 |
Discussion on local LMF |
ZTE Corporation, Sanechips |
| R2-2101922 |
Discussion on latency reduction of NR positioning |
ZTE Corporation, Sanechips |
| R2-2101923 |
Discussion on latency reduction of MO-LR |
ZTE Corporation, Sanechips |
| R2-2101950 |
Summary of AI 8.11.2.1 Latency analysis and latency enhancements |
CATT |
| R2-2102094 |
TP of [Post112-e][616][POS] TP for latency analysis results (Intel) |
Intel Corporation |
| R2-2102095 |
TP of [Post112-e][616][POS] TP for latency analysis results (Intel) |
Intel Corporation |
| R2-2102117 |
Report of [AT113-e][608][POS] Continue discussion of latency enhancements (CATT) |
CATT |
| R2-2102120 |
Text Proposals of latency enhancements |
CATT |
| R2-2102124 |
Text Proposals of latency enhancements |
CATT |
| R2-2102304 |
Report of [AT113-e][608][POS] Continue discussion of latency enhancements (CATT) |
CATT |
| R2-2102305 |
Text Proposals of latency enhancements |
CATT |
| 8.11.2.2 |
Accuracy and efficiency enhancements |
|
| R2-2100107 |
Discussion on on-demand DL-PRS |
OPPO |
| R2-2100108 |
Positioning in RRC_IDLE and RRC_INACTIVE state |
OPPO |
| R2-2100374 |
Discussion on Positioning in RRC Idle/Inactive mode |
InterDigital, Inc. |
| R2-2100375 |
Discussion on On-demand reference signals for positioning |
InterDigital, Inc. |
| R2-2100408 |
Further considerations on on-demand PRS |
CATT |
| R2-2100409 |
Further considerations on positioning in RRC_IDLE/RRC_INACTIVE |
CATT |
| R2-2100650 |
Support of positioning in idle/inactive mode |
Intel Corporation |
| R2-2100651 |
Support of on demand PRS |
Intel Corporation |
| R2-2100673 |
Discussion on positioning support in RRC_IDLE and INACTIVE |
Spreadtrum Communications |
| R2-2100684 |
Discussion on positioning support in RRC_IDLE and RRC_INACTIVE states |
vivo |
| R2-2100813 |
Discussion on PRS enhancements |
Xiaomi |
| R2-2100815 |
Positioning enhancements on RRC idle inactive UE |
Xiaomi |
| R2-2100866 |
Discussion on positioning accuracy and efficiency enhancements |
Apple |
| R2-2100916 |
Considerations on potential positioning enhancements |
Sony |
| R2-2100934 |
Positioning in RRC_INACTIVE and RRC_IDLE state |
Lenovo, Motorola Mobility |
| R2-2100935 |
On-Demand PRS Support |
Lenovo, Motorola Mobility |
| R2-2101225 |
Discussion on IDLE and INACTIVE positioning |
Huawei, HiSilicon |
| R2-2101226 |
Discussion on-demand PRS |
Huawei, HiSilicon |
| R2-2101229 |
TP for IDLE and INACTIVE postiioning |
Huawei, HiSilicon |
| R2-2101230 |
[Post112-e][609][POS] Positioning support in RRC_IDLE and INACTIVE (Huawei) |
Huawei, HiSilicon |
| R2-2101389 |
Report on [Post112-e][608][POS] Support of on-demand PRS |
Ericsson |
| R2-2101393 |
SDT, UL Positioning and On Demand PRS Aspects |
Ericsson |
| R2-2101470 |
Positioning of UEs in RRC Idle/Inactive State |
Qualcomm Incorporated |
| R2-2101471 |
On-Demand PRS |
Qualcomm Incorporated |
| R2-2101545 |
Summary for AI 8.11.2.2 on the accuracy and efficiency enhancements |
Intel Corporation |
| R2-2101868 |
Enhancements on on-demand PRS transmissions |
Nokia, Nokia Shanghai Bell |
| R2-2101908 |
support of positioning in idle/inactive mode UE |
Samsung R&D Institute UK |
| R2-2101909 |
Support of on-demand PRS |
Samsung R&D Institute UK |
| R2-2101920 |
Discussion on IDLE/INACTIVE mode positioning |
ZTE Corporation, Sanechips |
| R2-2102096 |
Text Proposal for on-demand PRS |
Ericsson |
| R2-2102336 |
Report of [609][POS] Continued discussion of positioning in idle/inactive (Huawei) |
Huawei, HiSilicon |
| R2-2102369 |
Summary of Email Discussion [AT113-e][610][POS] Continue discussion of on-demand PRS |
Ericsson |
| 8.11.3.1 |
General contributions |
|
| R2-2100596 |
[Post112-e][618][POS] Finalise integrity text proposals |
Swift Navigation |
| R2-2100719 |
Text Proposals of Definitions Relating to Positioning Integrity Modes |
Nokia, Nokia Shanghai Bell |
| R2-2101390 |
On RAT-dependent integrity use cases and error categories |
Ericsson |
| R2-2101504 |
Recommendations for the Integrity Text Proposal |
Swift Navigation, Intel Corporation |
| R2-2102092 |
[AT113-e][601][POS] Integrity text proposal |
Swift Navigation |
| R2-2102113 |
[AT113-e][601][POS] Integrity text proposal |
Swift Navigation |
| 8.11.3.2 |
Methodologies for network-assisted and UE-assisted integrity |
|
| R2-2100106 |
Discussion on Methodology for Integrity |
OPPO |
| R2-2100376 |
Discussion on Methodologies for network-assisted & UE-assisted integrity |
InterDigital, Inc. |
| R2-2100674 |
Discussion on the methodologies for network-assisted and UE-assisted integrity |
Spreadtrum Communications |
| R2-2100686 |
Discussion on methodologies for network-assisted and UE-assisted integrity |
vivo |
| R2-2100720 |
Positioning Integrity Result Reporting |
Nokia, Nokia Shanghai Bell |
| R2-2100812 |
Discussion on methodologies for positioning integrity |
Xiaomi |
| R2-2101087 |
UE Detection and Signalling of Percieved Threats to GNSS systems |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2101228 |
Discussion of network-assisted and UE-assisted integrity |
Huawei, HiSilicon |
| R2-2101391 |
GNSS Integrity Methodologies |
Ericsson |
| R2-2101436 |
Summary of AI 8.11.3.2 Methodologies for network-assisted and UE-assisted integrity |
ESA |
| R2-2101437 |
Text Proposal to methodologies for GNSS position integrity |
ESA |
| R2-2102100 |
Text proposal for IDLE and INACTIVE positioning |
Huawei, HiSilicon |
| R2-2102121 |
Text proposal for IDLE and INACTIVE positioning |
Huawei, HiSilicon |
| R2-2102431 |
Text proposal for IDLE and INACTIVE positioning-Ph2 |
Huawei, HiSilicon |
| 8.12.1 |
Organizational |
|
| R2-2100983 |
Conclusion of RedCap SI in RAN2 |
Ericsson |
| R2-2100984 |
RAN2 update to TR38875 |
Ericsson |
| R2-2102056 |
RAN2 update to TR38875 |
Ericsson |
| 8.12.2.1 |
Principles for how to define and constrain reduced capabilities |
|
| R2-2100310 |
Definition of RedCap UEs |
Qualcomm Incorporated |
| R2-2100460 |
UE type defination and constraining for RedCap UEs |
vivo, Guangdong Genius |
| R2-2100571 |
Define and constrain reduced capabilities for Redcap |
ZTE Corporation, Sanechips |
| R2-2100636 |
Methods for barring and for capability reporting |
Sierra Wireless, S.A. |
| R2-2100770 |
Discussion on intended use cases for RedCap Ues |
LG Electronics UK |
| R2-2101240 |
Further Discussions on UE Capability for RedCap |
CATT |
| R2-2101255 |
Higher layer capabilities and procedural impacts of RedCap UE |
Huawei, HiSilicon |
| R2-2101617 |
Discussion on the definition and constraining of reduced capabilities |
CMCC |
| R2-2102017 |
Summary of offline 107 - [REDCAP] L2 capabilties and UE types |
Huawei |
| R2-2102037 |
Summary of offline 107 - [REDCAP] L2 capabilties and UE types |
Huawei |
| 8.12.2.2 |
Identification and access restrictions |
|
| R2-2100155 |
Discussion on RedCap UE’s access control |
OPPO |
| R2-2100208 |
Supported bandwidth of RedCap UEs |
Samsung |
| R2-2100209 |
UAC enhancements for RedCap UE |
Samsung |
| R2-2100311 |
Impact of reduced capabilities on idle mode procedures |
Qualcomm Incorporated |
| R2-2100461 |
Identification and access restrictions for RedCap UEs |
vivo, Guangdong Genius |
| R2-2100572 |
Identification and access restrictions for Redcap |
ZTE Corporation, Sanechips |
| R2-2100652 |
UAC for RedCap UE |
Intel Corporation, Facebook |
| R2-2100721 |
Discussion on Identification and UE access restrictions for Redcap devices |
Xiaomi Communications |
| R2-2100722 |
Discussion on Identification and UE access restrictions for Redcap devices |
Xiaomi Communications |
| R2-2100723 |
Discussion on Identification and UE access restrictions for Redcap devices |
Xiaomi Communications |
| R2-2100755 |
Cell reselection of RedCap UE |
Fujitsu |
| R2-2100769 |
Discussion on identification and access restrictions |
LG Electronics UK |
| R2-2100985 |
TP for UE identification and access restriction |
Ericsson |
| R2-2101135 |
UAC enhancement for REDCAP UEs |
Lenovo, Motorola Mobility |
| R2-2101205 |
Cell access for REDCAP UE with reduced bandwidth |
Nokia, Nokia Shanghai Bell |
| R2-2101239 |
Further Discussion on Access Restriction |
CATT |
| R2-2101256 |
Identification and access restriction for RedCap UE |
Huawei, HiSilicon |
| R2-2101309 |
Cell access restrictions for REDCAP UE |
Nokia, Nokia Shanghai Bell |
| R2-2101630 |
Discussion on Early Identification |
CMCC |
| R2-2101949 |
Discussion on Early Identification |
CMCC |
| R2-2102018 |
Summary of offline 107 - [REDCAP] L2 capabilties and UE types |
Huawei |
| R2-2102039 |
Summary of offline 107 - [REDCAP] L2 capabilties and UE types |
Huawei |
| 8.12.3 |
UE power saving and battery lifetime enhancement |
|
| R2-2100156 |
Consideration on eDRX for RedCap UEs |
OPPO |
| R2-2100157 |
Discussion on RRM relaxation |
OPPO |
| R2-2100569 |
Report of Email discussion[155][REDCAP] RRM relaxations |
ZTE Corporation, Sanechips |
| R2-2100570 |
Consideration on interoperability between Rel-17 Redcap RRM relaxation and Rel-16 RRM relaxation |
ZTE Corporation, Sanechips |
| R2-2100581 |
RRM relaxation enhancement for RedCap UEs |
LG Electronics Inc. |
| R2-2101241 |
On eDRX for NR RRC Inactive and Idle |
CATT |
| R2-2101242 |
Summary of email discussion 154 - eDRX cycles |
CATT |
| R2-2101308 |
Power saving and battery lifetime enhancement for REDCAP UE |
Nokia, Nokia Shanghai Bell |
| R2-2101618 |
Discussion on the RRM relaxation |
CMCC |
| R2-2101797 |
Impact of eDRX PTW for Reduced Capability NR Devices |
Convida Wireless |
| 8.12.3.1 |
eDRX cycles |
|
| R2-2100343 |
Discussion on e-DRX for Redcap Devices |
Xiaomi Communications |
| R2-2100344 |
Discussion on e-DRX for Redcap Devices |
Xiaomi Communications |
| R2-2100986 |
Extended DRX for RRC_IDLE and RRC_INACTIVE for NR RedCap Ues |
Ericsson |
| R2-2101460 |
2.56 sec non-eDRX operation for RedCap |
Apple Inc, MediaTek Inc, Facebook Inc |
| 8.12.3.2 |
RRM relaxations |
|
| R2-2100312 |
Power saving enhancements for RedCap UEs |
Qualcomm Incorporated |
| R2-2100410 |
Discussion on RRM relaxation for RedCap UE |
Xiaomi Communications |
| R2-2100459 |
TP for TR 38875 on evaluation for RRM relaxation |
vivo, Guangdong Genius |
| R2-2100462 |
RRM relaxation for power saving |
vivo, Guangdong Genius |
| R2-2100805 |
RRM relaxation for RedCap UEs |
SHARP Corporation |
| R2-2100987 |
Further evaluations of RRM relaxation |
Ericsson |
| R2-2101114 |
RRM relaxation for stationary UE with reduced capability |
Lenovo, Motorola Mobility |
| R2-2101257 |
RRM measurement relaxation for RedCap UE |
Huawei, HiSilicon |
| R2-2101461 |
Localized mobility of some RedCap devices |
Apple Inc |
| R2-2101540 |
Relax measurement for stationary and low mobility devices |
Intel Corporation |
| R2-2101877 |
RRM relaxation for RedCap devices |
Samsung |
| R2-2102019 |
Summary of offline 109 - [REDCAP] eDRX cycles |
CATT |
| R2-2102020 |
Summary of offline 110 - [REDCAP] RRM relaxations |
ZTE |
| R2-2102038 |
Summary of offline 110 - [REDCAP] RRM relaxations |
ZTE |
| R2-2102040 |
Summary of offline 109 - [REDCAP] eDRX cycles |
CATT |
| R2-2102048 |
TP for RRM relaxations |
ZTE |
| 8.13.1 |
Organizational |
|
| R2-2100031 |
Reply LS on on energy efficiency (R3-207014; contact: Ericsson) |
RAN3 |
| R2-2100036 |
LS on UE based solution related to Logged MDT (R3-207176; contact: Ericsson) |
RAN3 |
| R2-2100047 |
LS on Mobility Enhancement Optimization (R3-207229; contact: Lenovo) |
RAN3 |
| R2-2100049 |
LS on corrections for F1-U delay reporting when gNB-DU and gNB-CU-UP are not split (R3-207233; contact: Ericsson) |
RAN3 |
| R2-2101424 |
On UE based solution related to Logged MDT (reply LS to R3-207176) |
Ericsson |
| R2-2102278 |
Reply LS on MDT Stage 2 and Stage 3 alignment (R3-211140; contact: Ericsson) |
RAN3 |
| 8.13.2 |
SON |
|
| R2-2100842 |
Consideration on handover related SON |
OPPO |
| R2-2101451 |
[Post112-e][853][NR R17 SON/MDT] R17 Information needed in UE report for CHO cases (Ericsson) |
Ericsson |
| R2-2102265 |
Summary of AI 8.13.2 - SON |
Ericsson |
| R2-2102447 |
Report of [Offline-888][NRR17 SONMDT] Indication for 2-step RACH (ZTE) |
ZTE Corporation, Sanechips |
| 8.13.2.1 |
Handover related SON aspects |
|
| R2-2100191 |
Further Consideration on CHO and DAPS Mobility Enhancement |
CATT |
| R2-2100600 |
Successful HO report |
Nokia, Nokia Shanghai Bell |
| R2-2100697 |
Discussion on scenarios, signalling and content for DAPS HO report |
vivo |
| R2-2100711 |
Discussion on RLF report in CHO case |
SHARP Corporation |
| R2-2100776 |
Discussion on successful handover report |
NTT DOCOMO, INC. |
| R2-2100780 |
Discussion on RLF report for DAPS |
SHARP Corporation |
| R2-2101102 |
SON Enhancements for CHO |
Lenovo, Motorola Mobility |
| R2-2101103 |
SON Enhancement for DAPS Handover |
Lenovo, Motorola Mobility |
| R2-2101251 |
Discussion on handover related SON aspects |
Huawei, HiSilicon |
| R2-2101343 |
SON aspects of DAPS HO and Fast MCG Recovery Optimizations |
QUALCOMM INCORPORATED |
| R2-2101438 |
CHO- and DAPS-related aspects of SON |
Ericsson |
| R2-2101586 |
Consideration on RLF report enhancements for CHO and DAPS |
ZTE Corporation, Sanechips |
| R2-2101595 |
RLF Enhancements for CHO |
Samsung |
| R2-2101602 |
RLF Enhancements for DAPS HO |
Samsung |
| R2-2101639 |
SON Enhancement for CHO |
CMCC |
| R2-2101640 |
SON Enhancement for DAPS |
CMCC |
| R2-2101668 |
Discussion on successive CHO failure scenarios |
Google Inc. |
| R2-2102145 |
[AT113-e][887][NR/R17 SON/MDT] Indication of candidate target cell (Ericsson) |
Ericsson |
| R2-2102146 |
The report of [Offline-e][886][NRR17 SONMDT] How to address time information (Qualcomm) |
Qualcomm |
| R2-2102435 |
The report of [Offline-e][886][NRR17 SONMDT] How to address time information (Qualcomm) |
Qualcomm |
| 8.13.2.2 |
2-step RA related SON aspects |
|
| R2-2100192 |
Discussion on RACH Report for 2-step RACH |
CATT |
| R2-2100286 |
Further discussion on SON aspects of 2-step RA |
China Telecommunication |
| R2-2100601 |
RACH report logging of 2-step and 4-step RACH information |
Nokia, Nokia Shanghai Bell |
| R2-2100698 |
Discussion on contents and signalling model of 2-step RACH report |
vivo |
| R2-2100710 |
Discussion on RA information for 2-step RA |
SHARP Corporation |
| R2-2101252 |
Discussion on 2 step RA related SON aspects |
Huawei, HiSilicon |
| R2-2101439 |
2-Step RA information for SON purposes |
Ericsson |
| R2-2101587 |
RA related enhancements |
ZTE Corporation, Sanechips |
| R2-2101603 |
RA Report Enhanements for 2-step RA |
Samsung |
| R2-2101641 |
SON Enhancement for 2-step RA |
CMCC |
| R2-2102269 |
Discussion on 2-step RACH reporting for SON |
OPPO |
| 8.13.2.3 |
Other WID related SON features |
|
| R2-2100193 |
Further Consideration on the UE RACH Report for SN |
CATT |
| R2-2100194 |
Enhancement on Mobility History Information |
CATT |
| R2-2100602 |
Refined UL Coverage Outage Detection |
Nokia, Nokia Shanghai Bell |
| R2-2100699 |
Discussion and reply on R3 LS for SgNB RACH report |
vivo |
| R2-2100700 |
Discussion on SON enhancements for Successful HO |
vivo |
| R2-2100748 |
Discussion on successful handover report |
NEC |
| R2-2100774 |
Discussion on collection of UE history information in EN-DC |
NTT DOCOMO, INC. |
| R2-2100779 |
Discussion on conditional PSCell addition/change failure report |
NTT DOCOMO, INC. |
| R2-2100845 |
Consideration on successful handover report and UE history information in EN-DC |
OPPO |
| R2-2101082 |
Discussion on rel-17 Radio Link Failure Report enhancement |
NTT DOCOMO INC. |
| R2-2101104 |
SON enhancement for Inter-RAT handover |
Lenovo, Motorola Mobility |
| R2-2101105 |
SON enhancement for fast MCG link recovery |
Lenovo, Motorola Mobility |
| R2-2101253 |
Discussion on other SON aspects |
Huawei, HiSilicon |
| R2-2101348 |
Successful Handover Report |
QUALCOMM INCORPORATED |
| R2-2101350 |
Open Issues in Other WID related SON features |
QUALCOMM INCORPORATED |
| R2-2101440 |
Other WID related SON features |
Ericsson |
| R2-2101588 |
Considerations on successful HO report |
ZTE Corporation, Sanechips |
| R2-2101589 |
Consideration on MHI and UL/DL imbalance |
ZTE Corporation, Sanechips |
| R2-2101604 |
SON Enhancements |
Samsung |
| R2-2101643 |
Discussion on Successful Handover Report |
CMCC |
| R2-2101644 |
Enhancement for Mobility History Information |
CMCC |
| 8.13.3 |
MDT |
|
| R2-2102143 |
Report of [AT113-e][844][NR/R17 SON/MDT] Logged MDT part I |
Huawei (Summary rapporteur) |
| 8.13.3.1 |
Immediate MDT enhancements |
|
| R2-2100195 |
Further Consideration on Immediate MDT Enhancements |
CATT |
| R2-2100493 |
On the need for enhancements to the MDT framework |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2100587 |
Immediate MDT with MR-DC and Intermediate MDT for early measurements |
Samsung Telecommunications |
| R2-2100588 |
Progressing Logged MDT for R17 concerning MR-DC, IRAT and IDC |
Samsung Telecommunications |
| R2-2100605 |
Delay measurement configuration for DC cases |
Nokia, Nokia Shanghai Bell |
| R2-2100701 |
Discussion on immediate MDT enhancements |
vivo |
| R2-2101342 |
On the configuration and accuracy of M5, M6, and M7 measurements in split-bearer |
QUALCOMM INCORPORATED |
| R2-2101414 |
On Immediate MDT Enhancements |
Ericsson |
| R2-2101590 |
Consideration on immediate MDT enhancements |
ZTE Corporation, Sanechips |
| R2-2101696 |
Discussion on immediate MDT enhancements |
Huawei, HiSilicon |
| R2-2101945 |
Progressing Logged MDT for R17 concerning MR-DC, IRAT and IDC |
Samsung Telecommunications |
| R2-2102250 |
Summary of 8.13.3 MDT |
Huawei |
| 8.13.3.2 |
Logged MDT enhancements |
|
| R2-2100196 |
Enhancement on Logged MDT in DC Scenario |
CATT |
| R2-2100287 |
Discussion on logged MDT in MR-DC |
China Telecommunication |
| R2-2100603 |
Enhancements for Logged MDT and RLFreporting |
Nokia, Nokia Shanghai Bell |
| R2-2100604 |
MDT use for management of System Information area |
Nokia, Nokia Shanghai Bell |
| R2-2100702 |
Discussion on logged MDT enhancements in EN-DC |
vivo |
| R2-2100843 |
Consideration of logged MDT enhancements |
OPPO |
| R2-2101341 |
Logged measurement Enhancements |
QUALCOMM INCORPORATED |
| R2-2101418 |
On logged MDT related enhancements |
Ericsson |
| R2-2101591 |
Consideration on Logged MDT enhancements and early measurements |
ZTE Corporation, Sanechips |
| R2-2101642 |
MDT enhancement for on-demand SI |
CMCC |
| R2-2101697 |
Discussion on logged MDT enhancements |
Huawei, HiSilicon |
| R2-2101960 |
Consideration of logged MDT enhancements |
OPPO |
| R2-2102142 |
Report of [AT113-e][845] [NR/R17 SON/MDT] Logged MDT part II (CMCC) |
CMCC |
| 8.13.4 |
L2 Measurements |
|
| R2-2100288 |
Discussion on L2 measurements for split bearers |
China Telecommunication |
| R2-2100703 |
Report of [Post112-e][852][NR R17 SONMDT] R17 L2M enhancement (vivo) |
vivo |
| R2-2101417 |
On layer-2 measurements |
Ericsson |
| R2-2101698 |
Discussion on L2M |
Huawei, HiSilicon |
| R2-2102147 |
The report of [Offline-822][NR R17 SONMDT] M6 (vivo) |
vivo (Rapporteur) |
| R2-2102149 |
LS on UE context keeping in the source cell |
RAN2 |
| R2-2102236 |
Summary for AI 8.13.4 L2 Measurements |
CMCC |
| R2-2102270 |
Discussion on M6 measurement for split bearer |
OPPO |
| R2-2102388 |
The report of [Offline-822][NR R17 SONMDT] M6 (vivo) |
vivo |
| 8.14 |
NR QoE SI |
|
| R2-2100034 |
NR QoE progress in RAN3 (R3-207120; contact: China Unicom) |
RAN3 |
| R2-2100039 |
LS on Framework for QoE Measurement Collection (R3-207189; contact: Nokia) |
RAN3 |
| R2-2100075 |
LS Reply on New service type of NR QoE (S4-201576; contact: Huawei) |
SA4 |
| R2-2100076 |
LS reply on QoE Measurement Collection (S4-201600; contact: Ericsson) |
SA4 |
| R2-2100079 |
LS on QoE Measurement Collection (S5-205347; contact: Ericsson) |
SA5 |
| R2-2100597 |
Generic requirements for QMC in NR |
Nokia, Nokia Shanghai Bell |
| R2-2100598 |
QMC procedures principles |
Nokia, Nokia Shanghai Bell |
| R2-2100706 |
Discussion on QoE configuration and reporting |
vivo |
| R2-2100846 |
Discussion on QoE measurement collection in NR |
OPPO |
| R2-2100879 |
Discussions on the QoE SI Metrics and Collection Procedures |
Apple |
| R2-2100967 |
Discussion on NR QoE |
CATT |
| R2-2100995 |
QoE measurements in NR |
LG Electronics Inc. |
| R2-2101189 |
Discussion on QoE configuration and report aspects |
Huawei, HiSilicon |
| R2-2101190 |
Discussion on QoE handling during UE mobility |
Huawei, HiSilicon |
| R2-2101191 |
Discussion on other QoE aspects |
Huawei, HiSilicon |
| R2-2101271 |
Solution for QoE Management |
Ericsson |
| R2-2101272 |
Mobility Support for NR QoE Management |
Ericsson |
| R2-2101273 |
Analysis of QoE measurements at OAM and RAN |
Ericsson |
| R2-2101336 |
LS reply on QoE Measurement Collection |
QUALCOMM INCORPORATED |
| R2-2101338 |
Handling of NR QoE measurements |
QUALCOMM INCORPORATED |
| R2-2101339 |
Handling of NR QoE reporting |
QUALCOMM INCORPORATED |
| R2-2101496 |
Ranking and prioritization of QoE enhancement features |
QUALCOMM Incorporated |
| R2-2101581 |
Discussion on the RAN2 related work on NR QoE |
China Unicom |
| R2-2101806 |
Discussion on NR QoE management |
CMCC |
| R2-2101878 |
Transport of NR QoE report |
Samsung |
| R2-2101879 |
RRC signaling for NR QoE |
Samsung |
| R2-2101880 |
Alignment with RAN3 agreements for NR QoE |
Samsung |
| R2-2101917 |
Miscellaneous discussion on QoE |
ZTE Corporation, Sanechips |
| R2-2101918 |
Discussion on NR QoE continuity during handover |
ZTE Corporation, Sanechips |
| R2-2101919 |
Stop an ongoing QoE measurement reporting |
ZTE Corporation, Sanechips |
| R2-2102243 |
Summary document on AI 8.14 NR QoE SI |
China Unicom |
| R2-2102367 |
Summary of [AT113-e][039][eQoE] RAN2 conclusions on QoE (China Unicom) |
China Unicom |
| R2-2102368 |
TP for TR update (RAN2) |
China Unicom |
| R2-2102414 |
LS reply on QoE Measurement Collection |
RAN2 |
| R2-2102417 |
LS reply on QoE Measurement Collection |
Qualcomm |
| R2-2102483 |
TP for TR update (RAN2) |
China Unicom |
| R2-2102500 |
LS reply on QoE Measurement Collection |
RAN2 |
| 8.15.1 |
Organizational |
|
| R2-2100019 |
Reply LS on new PQI support for PC5 communication (R1-2009621; contact: OPPO) |
RAN1 |
| R2-2100105 |
Discussion on SA2 LS on sidelink DRX |
OPPO |
| R2-2100798 |
Draft Reply LS on PC5 DRX operation |
vivo |
| R2-2101726 |
(Draft) Reply LS on SA2 on PC5 DRX operation |
LG Electronics France |
| R2-2102182 |
Reply LS on PC5 DRX operation |
RAN2 |
| 8.15.2.1 |
SL DRX general |
|
| R2-2100235 |
Sidelink DRX Granularity |
CATT |
| R2-2100236 |
Sidelink DRX Timer Maintainence and Active Time Definition |
CATT |
| R2-2100272 |
Left issues on definition of SL DRX functionality |
OPPO |
| R2-2100274 |
Discussion on granularity for sidelink DRX |
OPPO |
| R2-2100496 |
Discussion on principles for sidelink DRX |
ZTE Corporation, Sanechips |
| R2-2100497 |
Discussion on timer configuration for sidelink DRX |
ZTE Corporation, Sanechips |
| R2-2100514 |
Definition of the Active Time in SL DRX |
InterDigital |
| R2-2100515 |
Procedures for Handling the DRX Configuration |
InterDigital |
| R2-2100536 |
General aspects for SL DRX |
Ericsson |
| R2-2100573 |
General Principle of NR SL DRX |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100622 |
On general Sidelink DRX design |
Intel Corporation |
| R2-2100637 |
Discussion on SL DRX |
LG Electronics France |
| R2-2100638 |
Discussion on SL DRX Timer |
LG Electronics France |
| R2-2100690 |
[draft] LS to RAN1 on SL DRX timer configuration |
ZTE Corporation, Sanechips |
| R2-2100795 |
SL DRX remaining issues |
vivo |
| R2-2100862 |
Discussion on remaining issues on SL DRX Configuration |
Apple |
| R2-2101224 |
Discontinuous reception and transmission in SL |
Lenovo, Motorola Mobility |
| R2-2101245 |
Discussion on Sidelink DRX |
Qualcomm Finland RFFE Oy |
| R2-2101323 |
Backward Compatibility Issue of SL DRX with Rel.16 Sidelink |
Nokia, Nokia Shanghai Bell |
| R2-2101330 |
Granularity of SL DRX operation |
Samsung Research America |
| R2-2101600 |
Discussion on sidelink DRX timer handling |
Xiaomi communications |
| R2-2101723 |
Consideration on sidelink DRX for groupcast and broadcast |
Huawei, HiSilicon |
| R2-2101725 |
General aspects of SL DRX for unicast |
Huawei, HiSilicon |
| R2-2101727 |
Summary of [POST112-e][702][SLe] High-level principles for SL DRX |
LG Electronics France |
| R2-2101756 |
Discussion on Sidelink DRX |
ASUSTeK |
| R2-2102183 |
Summary of [AT113-e][707] |
OPPO |
| R2-2102184 |
Summary of [AT113-e][708] |
Lenovo, Motorola Mobility |
| 8.15.2.2 |
Mechanism to align wake-up time between TX and RX UEs |
|
| R2-2100237 |
Sidelink DRX Configuration Procedure for Sidelink Unicast |
CATT |
| R2-2100273 |
Discussion on configuration for sidelink DRX |
OPPO |
| R2-2100421 |
Reservation Chain-based DRX Power Saving |
Fujitsu |
| R2-2100422 |
Alignment of Wake-up Time between TX and RX UEs |
Fujitsu |
| R2-2100495 |
Discussion on Mechanism to align wake-up time between TX and RX UEs |
ZTE Corporation, Sanechips |
| R2-2100539 |
SL DRX alignment between two UEs |
Ericsson |
| R2-2100574 |
NR SL DRX Alignment between UEs |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100629 |
Alignment of DRX active time among sidelink UEs |
Intel Corporation |
| R2-2100657 |
Inter-UE sidelink DRX wake-up time alignment |
Spreadtrum Communications |
| R2-2100796 |
Mechanism to align wake-up time between TX and RX UEs |
vivo |
| R2-2100863 |
Discussion on HARQ related timers in SL DRX |
Apple |
| R2-2101117 |
Discussion on wake-up time alignment between Tx and Rx UEs |
Lenovo, Motorola Mobility |
| R2-2101192 |
Issue with SL DRX Inactivity Timer for SL groupcast |
Nokia, Nokia Shanghai Bell |
| R2-2101207 |
SL DRX with pre-indicated resources |
Nokia, Nokia Shanghai Bell |
| R2-2101209 |
On the discrepancy TX-centric vs. RX-centric in Sidelink DRX |
Nokia, Nokia Shanghai Bell |
| R2-2101246 |
On Wake-up alignment between Tx and Rx UEs |
Qualcomm Finland RFFE Oy |
| R2-2101331 |
Alignment of wake-up time between TX and RX UEs |
Samsung Research America |
| R2-2101598 |
DRX coordination between TX and RX UE |
Xiaomi communications |
| R2-2101645 |
On aligning wake-up time between TX and RX UEs |
MediaTek Inc. |
| R2-2101652 |
Sidelink DRX Considerations |
Convida Wireless |
| R2-2101706 |
Discussion on SL DRX wake-up time alignment between inter-UEs |
LG Electronics France |
| R2-2101762 |
Consideration on the sidelink DRX for unicast |
Huawei, Hisilicon |
| R2-2101866 |
Methods for aligning SL DRX between UEs |
Sierra Wireless, S.A. |
| 8.15.2.3 |
Coordination between Uu DRX and SL DRX |
|
| R2-2100275 |
Discussion on network involvement for SL related DRX |
OPPO |
| R2-2100494 |
Discussion on Coordination between Uu DRX and SL DRX |
ZTE Corporation, Sanechips |
| R2-2100538 |
DRX alignment between Uu and SL |
Ericsson |
| R2-2100575 |
NR SL DRX Uu and SL Wake-Up Time |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100623 |
Alignment of Uu and SL DRX active time |
Intel Corporation |
| R2-2100797 |
Coordination between Uu DRX and SL DRX |
vivo |
| R2-2100864 |
Discussion on alignment of Uu DRX and SL DRX |
Apple |
| R2-2100917 |
Discussion on Sidelink DRX and sensing |
Sony |
| R2-2100931 |
Coordination between Uu DRX and SL DRX |
Lenovo, Motorola Mobility |
| R2-2101247 |
On coordination between Uu DRX and SL DRX |
Qualcomm Finland RFFE Oy |
| R2-2101306 |
On configuration and operation of SL DRX |
Nokia, Nokia Shanghai Bell |
| R2-2101332 |
Coordination between DL DRX and SL DRX |
Samsung Research America |
| R2-2101599 |
DRX coordination between Uu and sidelink |
Xiaomi communications |
| R2-2101646 |
On coordination between Uu DRX and SL DRX |
MediaTek Inc. |
| R2-2101763 |
Discussion on SL communication impact on Uu DRX |
Huawei, Hisilicon |
| R2-2101764 |
Alignment between Uu DRX and SL DRX |
Huawei, Hisilicon |
| R2-2101791 |
Alignment scheme for Uu DRX and SL DRX |
LG Electronics Inc. |
| R2-2101855 |
Methods for configuring SL DRX relative to Uu DRX |
Sierra Wireless, S.A. |
| 8.15.2.4 |
Others |
|
| R2-2100238 |
Impacts of Sidelink DRX on the Other Procedures |
CATT |
| R2-2100499 |
Discussion on sensing and DRX |
ZTE Corporation, Sanechips |
| R2-2100537 |
Interaction between partial sensing and DRX |
Ericsson |
| R2-2101333 |
Transmission UE behaviours for SL DRX |
Samsung Research America |
| R2-2101869 |
View on resource selection in mode 2 |
ITL |
| 8.15.3 |
Resource allocation enhancements RAN2 scope |
|
| R2-2100239 |
Consideration on the Resource Allocation Enhancements |
CATT |
| R2-2100240 |
Mixing Blind and Feedback-based HARQ Retransmissions |
CATT |
| R2-2100276 |
Discussion on inter-UE coordination |
OPPO |
| R2-2100423 |
Dual-mode Configuration and Selection Mechanism for NR Sidelink |
Fujitsu |
| R2-2100498 |
Discussion on inter-UE coordination |
ZTE Corporation, Sanechips |
| R2-2100516 |
Performing Mode 2 Resource Allocation when configured with SL DRX |
InterDigital |
| R2-2100517 |
[DRAFT] LS on RAN1 impact on sidelink DRX |
InterDigital |
| R2-2100518 |
RAN2 Aspects of Resource Allocation with Inter-UE Coordination |
InterDigital |
| R2-2100576 |
Inter-UE Coordination for Sidelink Mode 2 Resource Allocation |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100577 |
Power Reduction for Sidelink Mode 2 Resource Allocation |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2100613 |
Resource Allocation Enhancements for Power Saving |
Intel Corporation |
| R2-2100659 |
Discussion on resource allocation enhancement for NR sidelink |
Spreadtrum Communications |
| R2-2100799 |
Uu and SL DRX impact to resource allocation mode 1 |
vivo |
| R2-2100800 |
SL DRX impact to resource allocation mode 2 |
vivo |
| R2-2100865 |
Discussion on resource allocation for Pedestrian UE |
Apple |
| R2-2100981 |
General principles of resource allocation enhacements for SL mode 2 |
Ericsson |
| R2-2100982 |
Way forward for resource allocation enhacements for SL mode 2 |
Ericsson |
| R2-2101116 |
Discussion on sidelink resource allocation enhancements |
Lenovo, Motorola Mobility |
| R2-2101299 |
Inter-UE Coordination for Enhanced Reliability |
Intel Corporation |
| R2-2101303 |
Congestion control for Resource Allocation Schemes in NR Sidelink |
Intel Corporation |
| R2-2101318 |
Coexistence of Sensing-based and Random Selection for Sidelink Mode 2 Resource Allocation |
Nokia, Nokia Shanghai Bell |
| R2-2101334 |
Random selection and partial sensing |
Samsung Research America |
| R2-2101335 |
Inter-UE coordination |
Samsung Research America |
| R2-2101647 |
Transmission of assistance information for Mode 2 enhancement |
MediaTek Inc. |
| R2-2101650 |
On Resource Allocation Mode 2 Enhancement for NR Sidelink |
Convida Wireless |
| R2-2101724 |
Consideration on resource allocation enhancement in Rel-17 NR SL enhancement |
Huawei, HiSilicon |
| R2-2101795 |
Power efficient resource allocation |
LG Electronics Inc. |
| R2-2101796 |
Inter-UE coordination for NR V2X |
LG Electronics Inc. |
| 8.15.4 |
Other |
|
| R2-2100519 |
Discussion on Uu DRX for SL UE |
InterDigital |
| R2-2101648 |
On SL sync search optimization |
MediaTek Inc. |
| 8.16.1 |
Organizational |
|
| R2-2100542 |
RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN |
Nokia, China Telecom (Rapporteurs) |
| 8.16.2 |
Support SNPN with subscription or credentials by a separate entity |
|
| R2-2100241 |
Initial Discussion on Credential by a Separate Entity |
OPPO |
| R2-2100277 |
Consideration on SNPN with Subscription or Credentials by a Separate Entity |
CATT |
| R2-2100289 |
Discussion of credentials by a separate entity in SNPN |
China Telecommunication |
| R2-2100431 |
Consideration on the Separate Entity Supporting |
ZTE Corporation, Sanechips |
| R2-2100441 |
Access to SNPN with credentials from a different entity |
Qualcomm Incorporated |
| R2-2100490 |
SNPN and Service Provider (SP) separation |
Ericsson |
| R2-2100543 |
Overview of RAN2 impacts to support SNPN with 3rd party subscription |
Nokia, Nokia Shanghai Bell |
| R2-2100634 |
RAN2 impact on support SNPN along with subscription / credentials owned by an entity separate from the SNPN |
Intel Corporation |
| R2-2100838 |
Support SNPN with subscription or credentials by a separate entity |
vivo |
| R2-2100918 |
SIB info for third party credentials and UE onboarding |
Sony |
| R2-2101001 |
Discussion on RAN2 impact of supporting SNPN with credentials owned by a separate entity |
Huawei, HiSilicon, China Telecom |
| R2-2101515 |
Support of SNPN with subscription or credentials by a separate entity |
LG Electronics |
| R2-2101717 |
Support SNPN along with credentials owned by an entity separate from the SNPN |
CMCC |
| R2-2102362 |
Summary of [AT113-e][031][eNPN] SNPN with subscription or credentials by a separate entity |
Nokia |
| R2-2102413 |
Summary of [AT113-e][031][eNPN] SNPN with subscription or credentials by a separate entity |
Nokia |
| R2-2102489 |
Clarification request for eNPN features |
RAN2 |
| 8.16.3 |
Support UE onboarding and provisioning for NPN |
|
| R2-2100242 |
Initial Discussion for Onboarding |
OPPO |
| R2-2100243 |
Cell Access Control for Onboarding |
OPPO |
| R2-2100278 |
Discussion on UE Onboarding and Provisioning for NPN |
CATT |
| R2-2100432 |
Consideration on the Onboarding and Provisioning for NPN |
ZTE Corporation, Sanechips |
| R2-2100442 |
UE onboarding and provisioning for NPN |
Qualcomm Incorporated |
| R2-2100491 |
UE onboarding |
Ericsson |
| R2-2100544 |
Overview of RAN2 impacts to support UE onboarding and provisioning for NPN |
Nokia, Nokia Shanghai Bell |
| R2-2100635 |
RAN2 impact on support UE onboarding and provisioning for NPN |
Intel Corporation |
| R2-2100839 |
Support UE onboarding and provisioning for NPN |
vivo |
| R2-2101002 |
Discussion on RAN2 impact of UE onboarding and remote provisioning for SNPN and PNI-NPN |
Huawei, HiSilicon, China Telecom |
| R2-2101516 |
Support of UE onboarding and provisioning for NPN |
LG Electronics |
| R2-2101616 |
Discussion the issue to support UE onboarding and provisioning for NPN |
CMCC |
| R2-2101898 |
LS on UE onboarding and remote provisioning for SNPN |
CMCC |
| R2-2101930 |
draft LS on UE onboarding and remote provisioning for SNPN |
CMCC |
| R2-2102363 |
Summary of [AT113-e][032][eNPN] UE onboarding and provisioning for NPN |
Ericsson (email discussion Rapporteur) |
| 8.16.4 |
Other |
|
| R2-2100279 |
Discussion on Support of IMS Emergency for SNPN |
CATT |
| R2-2100364 |
RAN2 impact on support of IMS emergency call for SNPN |
Intel Corporation |
| R2-2100433 |
Consideration on the IMS voice and emergency services for SNPN |
ZTE Corporation, Sanechips |
| R2-2100492 |
Support of IMS voice and emergency services for SNPNs |
Ericsson |
| R2-2100545 |
Overview of RAN2 impacts to support IMS and emergency services for SNPN |
Nokia, Nokia Shanghai Bell |
| R2-2100639 |
Support of IMS voice and emergency services for SNPN |
Qualcomm Incorporated |
| R2-2100840 |
Support of IMS voice and emergency service for SNPN |
vivo |
| R2-2101003 |
Discussion on support of IMS voice and emergency services for SNPN |
Huawei, HiSilicon, China Telecom |
| R2-2101517 |
Support of IMS voice and emergency services for SNPN |
LG Electronics |
| R2-2101631 |
Support of IMS voice and emergency services for SNPN |
CMCC |
| R2-2102309 |
Summary for Offline [033][eNPN] IMS voice and emergency services for SNPN |
Huawei, HiSilicon |
| 8.17 |
NR R17 Other |
|
| R2-2100046 |
LS on broadcasting gNB ID length in system information block (R3-207226; contact: Ericsson) |
RAN3 |
| R2-2100054 |
LS for FR2 FWA power class (R4-2016876; contact: Softbank) |
RAN4 |
| R2-2100055 |
LS on removing restriction on configuring UL MIMO for SUL band (R4-2016909; contact: CMCC) |
RAN4 |
| R2-2100068 |
LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (S2-2009227; contact: Tencent) |
SA2 |
| R2-2100069 |
LS on Aerial Features for Unmanned Aerial Vehicles (S2-2009228; contact: Qualcomm) |
SA2 |
| R2-2100896 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei |
| R2-2100897 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei |
| R2-2100950 |
Introduction of PC5 for FR2 |
Nokia, Nokia Shanghai Bell |
| R2-2100951 |
Introduction of PC5 for FR2 |
Nokia, Nokia Shanghai Bell |
| R2-2100952 |
Introduction of PC5 for FR2 |
Nokia, Nokia Shanghai Bell |
| R2-2100953 |
Introduction of PC5 for FR2 |
Nokia, Nokia Shanghai Bell |
| R2-2101032 |
Discussion on NeedForGap signalling in MR-DC |
Nokia, Nokia Shanghai Bell, BT Plc |
| R2-2101415 |
On broadcasting gNB ID length in SIB1 (reply LS to R3-207226) |
Ericsson |
| R2-2101457 |
Support of 35 MHz and 45 MHz channel bandwidth for FR1 |
Apple Inc, T-Mobile |
| R2-2101458 |
Support of 35 MHz and 45 MHz channel bandwidth for FR1 |
Apple Inc, T-Mobile |
| R2-2101477 |
Discussion on Capturing PDCP Impacts for User Plane Integrity Protection |
Ericsson |
| R2-2101612 |
Draft CR: Remove the maximum number of MIMO layers configuration restrictions for SUL |
CMCC, Huawei, HiSilicon, CATT |
| R2-2101613 |
Draft CR: Remove the maximum number of MIMO layers restrictions for SUL |
CMCC, Huawei, HiSilicon, CATT |
| R2-2102259 |
LS to RAN2 on 35 and 45 MHz channel Bandwidths (R4-2017846; contact: T-Mobile) |
RAN4 |
| R2-2102332 |
Draft LS response on broadcasting gNB ID length in system information block |
Ericsson |
| R2-2102335 |
Draft CR: Remove the maximum number of MIMO layers configuration restrictions for SUL |
CMCC, Huawei, HiSilicon, CATT |
| R2-2102375 |
Summary of [AT113-e][034][NR17 Other] NR17 other (Huawei) |
Huawei, HiSilicon |
| R2-2102393 |
Support of 35 MHz and 45 MHz channel bandwidth for FR1 |
Apple Inc, T-Mobile |
| R2-2102394 |
Support of 35 MHz and 45 MHz channel bandwidth for FR1 |
Apple Inc, T-Mobile |
| R2-2102432 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei, Nokia |
| R2-2102433 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei, Nokia |
| R2-2102449 |
Reply LS on broadcasting gNB ID length in system information block |
RAN2 |
| R2-2102451 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei, Nokia |
| R2-2102452 |
Introducing UE capability for power class 5 for FR2 FWA |
SoftBank, Huawei, Nokia |
| R2-2102453 |
Remove the maximum number of MIMO layers configuration restrictions for SUL |
CMCC, Huawei, HiSilicon, CATT |
| R2-2102454 |
Remove the maximum number of MIMO layers restrictions for SUL |
CMCC, Huawei, HiSilicon, CATT |
| 9.1.1 |
Organizational |
|
| R2-2101552 |
Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC |
Ericsson |
| R2-2102164 |
RAN2 agreements for Rel-17 NB-IoT and LTE-MTC |
Document Rapporteur (Ericsson) |
| 9.1.2 |
NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF |
|
| R2-2100324 |
Further considerations on measurement in connected mode |
ZTE Corporation, Sanechips |
| R2-2100325 |
draft LS on measurement in connected mode for NB-IoT |
ZTE Corporation, Sanechips |
| R2-2100513 |
Analysis on Re-establishment time components and Solutions for Faster re-establishment |
Nokia, Nokia Shanghai Bell |
| R2-2100670 |
Further discussion on the corresponding measurement before RLF |
Spreadtrum Communications |
| R2-2101043 |
Neighbour cell measurements in RRC_CONNECTED |
Huawei, HiSilicon |
| R2-2101056 |
Impact on Static Devices |
THALES |
| R2-2101113 |
Neighbor cell measurements triggering before RLF |
Lenovo, Motorola Mobility |
| R2-2101157 |
Way forward for connected mode neighbour cell measurement in NB-IoT |
Qualcomm Incorporated |
| R2-2101329 |
On the solution for reduction of RLF detection time |
Nokia Solutions & Networks (I) |
| R2-2101396 |
Reducing time taken for reestablishment procedures in NB-IoT |
Ericsson |
| R2-2101397 |
Summary of NB-IoT AI 9.1.2 neighbor cell measurements before RLF |
Ericsson |
| R2-2101399 |
draft LS Measurements for Reducing time for RRC Reestablishment |
Ericsson |
| R2-2101836 |
Measurement before radio link failure |
MediaTek Inc. |
| R2-2102154 |
Summary of Email Discussion [AT113-e][304][NBIOT/eMTC R17] Neighbour cell measurements before RLF |
Ericsson |
| R2-2102156 |
[Draft] LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state |
Ericsson |
| R2-2102163 |
[Draft] LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state |
Ericsson |
| R2-2102165 |
LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state |
RAN2 |
| 9.1.3 |
NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration |
|
| R2-2100326 |
Paging carriers configuration and selection |
ZTE Corporation, Sanechips |
| R2-2100512 |
Paging carrier selection procedure based on CEL |
Nokia, Nokia Shanghai Bell |
| R2-2100671 |
Further discussion on enhanced paging carrier selection and NPRACH carrier selection |
Spreadtrum Communications |
| R2-2101044 |
Paging carrier selection improvements |
Huawei, HiSilicon |
| R2-2101045 |
Summary of contributions on Paging carrier selection improvements |
Huawei |
| R2-2101156 |
Support for NB-IoT carrier selection based on the coverage level |
Qualcomm Incorporated |
| R2-2101395 |
NB-IoT carrier selection and configuration based on coverage level |
Ericsson |
| R2-2101839 |
Carrier selection enhancement |
MediaTek Inc. |
| R2-2102155 |
Summary of [AT113-e][305][NBIOT R17] Paging carrier selection improvements |
Huawei |
| 9.1.4 |
Other |
|
| R2-2101046 |
Discussion on 16-QAM for NB-IoT |
Huawei, HiSilicon |
| R2-2101047 |
Support of 14 HARQ Processes in DL, for HD-FDD Cat M1 Ues |
Huawei, HiSilicon |
| R2-2101398 |
Support of 16-QAM for unicast in UL and DL in NB-IoT |
Ericsson |
| 9.2 |
SI on NB-IoT and eMTC support for NTN |
|
| R2-2101455 |
Skeleton TR 36.763 Study NB-IoT / eMTC support for NTN |
MediaTek Inc. |
| 9.2.1 |
Organizational and scenarios |
|
| R2-2100002 |
Timer for periodic network selection attempts in satellite access (C1-207766; contact: OPPO) |
CT1 |
| R2-2101052 |
Discussion on scenarios for NTN NB-IoT |
Huawei, HiSilicon |
| R2-2101258 |
Market expectations for IoT over NTN |
NOVAMINT |
| R2-2101401 |
Draft LS on IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2101408 |
IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2101409 |
FS_LTE_NBIOT_eMTC_NTN work plan |
Eutelsat S.A. |
| R2-2101553 |
IoT NTN scenarios and architecture |
Ericsson |
| R2-2102244 |
Draft LS on IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2102245 |
IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2102246 |
Text proposal for TR 36.763 related to RAN2 |
Eutelsat S.A. |
| R2-2102255 |
Market expectations for IoT over NTN |
Novamint, Siemens, Philips, EUTC, EDF, b-com
Sateliot, Gatehouse |
| R2-2102257 |
Draft LS on IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2102258 |
IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2102271 |
Draft LS on IoT-NTN basic architecture |
Eutelsat S.A. |
| R2-2102418 |
Text proposal for TR 36.763 related to RAN2 |
Eutelsat S.A. |
| R2-2102420 |
LS on IoT-NTN basic architecture |
RAN2 |
| R2-2102475 |
Text proposal for TR 36.763 related to RAN2 |
Eutelsat S.A. |
| R2-2102492 |
Text proposal for TR 36.763 related to RAN2 |
Eutelsat S.A. |
| R2-2102501 |
LS on IoT-NTN basic architecture |
RAN2 |
| R2-2102502 |
Text proposal for TR 36.763 capturing R2#113e agreements |
Eutelsat, MediaTek |
| 9.2.2 |
User Plane |
|
| R2-2100165 |
Discussion on UP issues for IoT over NTN |
OPPO |
| R2-2100180 |
IOT NTN user plane related issues |
Beijing Xiaomi Mobile Software |
| R2-2100265 |
On Disabling HARQ Retransmissions in IoT-NTN |
MediaTek Inc. |
| R2-2100329 |
Consideration on user plane of IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2100736 |
Enhancement to HARQ process |
Qualcomm Incorporated |
| R2-2100737 |
Applicability of eMTC and NB-IoT feature in NTN |
Qualcomm Incorporated |
| R2-2101053 |
Discussion on User Plane for NTN NB-IoT |
Huawei, HiSilicon |
| R2-2101064 |
Discussion on IoT over NTN HARQ enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2101130 |
Considerations on PUR in IoT NTN |
Lenovo, Motorola Mobility |
| R2-2101554 |
HARQ operation and timers for IoT NTN |
Ericsson |
| R2-2102251 |
Summary of AI 9.2.2 on user plane for IoT NTN |
OPPO |
| 9.2.3 |
Mobility and Tracking Area |
|
| R2-2100166 |
Discussion on connected mode mobility for IoT over NTN |
OPPO |
| R2-2100167 |
Discussion on idle mode procedure for IoT over NTN |
OPPO |
| R2-2100257 |
IoT NTN Observations and Proposals |
Lockheed Martin |
| R2-2100263 |
Improving Tracking Area Updates in IoT-NTN |
MediaTek Inc. |
| R2-2100264 |
On Efficient Cell Re-selection in IoT-NTN |
MediaTek Inc. |
| R2-2100266 |
Connected Mode Mobility in IoT-NTN |
MediaTek Inc. |
| R2-2100338 |
Consideration on control plane of IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2100510 |
Analysis of mobility aspects for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2100541 |
Discussion on the service link discontinuity and affected procedures for NB-IoT NTN |
Gatehouse, Sateliot |
| R2-2100738 |
Connected mode and idle mode mobility |
Qualcomm Incorporated |
| R2-2100807 |
Discussion on connected mode mobility in NB-IoT and eMTC NTN |
Xiaomi |
| R2-2100808 |
Cell selection and reselection for IoT NTN |
Xiaomi |
| R2-2101054 |
Discussion on Mobility and TA for NTN NB-IoT |
Huawei, HiSilicon |
| R2-2101131 |
Discontinuous coverage for IoT NTN |
Lenovo, Motorola Mobility |
| R2-2101132 |
RLF-based mobility for NB-IoT in NTN |
Lenovo, Motorola Mobility |
| R2-2101248 |
Discussion on the service link discontinuity and affected procedures for NB-IoT NTN |
Gatehouse, Sateliot |
| R2-2101555 |
Idle and connected mode mobility for IoT NTN |
Ericsson |
| R2-2102248 |
Summary for Control Plane Procedures in IoT-NTN |
MediaTek Inc. |
| R2-2102419 |
Summary for Control Plane Procedures in IoT-NTN |
MediaTek Inc. |
| R2-2102494 |
Summary for Control Plane Procedures in IoT-NTN |
MediaTek Inc. |
| 9.2.4 |
Other |
|
| R2-2100168 |
Discussion on system information enhancement for IoT over NTN |
OPPO |
| R2-2100339 |
Consideration on other aspects of IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2100511 |
Applicability terrestrial IoT Features for IoT-NTN study |
Nokia, Nokia Shanghai Bell |
| R2-2100739 |
Enhancement to SIB acquisition |
Qualcomm Incorporated |
| R2-2101055 |
Discussion on SI for NTN NB-IoT |
Huawei, HiSilicon |
| R2-2101065 |
On timing and channel repetition impact in LEO |
Nokia, Nokia Shanghai Bell |
| R2-2101556 |
Connection density evaluation for IoT NTN devices |
Ericsson |
| 9.3 |
EUTRA R17 Other |
|
| R2-2100003 |
User location identification from Carrier Aggregation secondary cell activation messages (FSAG Doc 88_009; contact: GSMA) |
GSMA |
| R2-2100483 |
UE location attack based on SCell activation |
Ericsson |
| R2-2100645 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, Samsung |
| R2-2100818 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, Samsung |
| R2-2100819 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, Samsung |
| R2-2100821 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, Samsung |
| R2-2100823 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, Samsung |
| R2-2100939 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation |
| R2-2101808 |
Introduction of event-based trigger for LTE MDT logging |
KDDI Corporation, CMCC, Samsung |
| R2-2101831 |
Discussion on user location identification from SCell Activation message |
Huawei, HiSilicon |
| 9.4 |
NR and EUTRA Inclusive language |
|
| R2-2100081 |
LS on Use of Inclusive Language in 3GPP (SP-201143; contact: Intel) |
SA |
| R2-2100689 |
Inclusive Language Review |
Nokia (Rapporteur) |
| R2-2100691 |
Inclusive Language Handling |
Nokia, Nokia Shanghai Bell |
| R2-2100956 |
Inclusive language in 36.300 |
Nokia (Rappporteur) |
| R2-2101079 |
Inclusive language in 36.304 |
Nokia, Nokia Shanghai Bell |
| R2-2101287 |
Inclusive language |
Ericsson |
| R2-2101454 |
Inclusive language in 37.320 |
Nokia (Rapporteur) |
| R2-2101472 |
Introduction of inclusive language in RAN2 specifications |
Intel Corporation |
| R2-2101961 |
Offline 201 on Inclusive Language |
Nokia (Rapporteur) |
| R2-2101986 |
Reply LS on Use of Inclusive Language in 3GPP |
RAN2 |
| R2-2101987 |
Inclusive language |
Ericsson |
| R2-2101988 |
Inclusive language in TS36.331 |
Samsung (Rapporteur) |
| R2-2101989 |
Inclusive language in 36.300 |
Nokia (Rappporteur) |
| R2-2101990 |
Inclusive language in 36.304 |
Nokia, Nokia Shanghai Bell |
| R2-2101991 |
Inclusive language in 37.320 |
Nokia (Rapporteur) |
| R2-2101992 |
Inclusive language in TS38.306 |
Intel (Rapporteur) |
| R2-2102005 |
Offline 201 on Inclusive Language |
Nokia (Rapporteur) |
| R2-2102281 |
Inclusive Language Review for TS 38.300 |
Nokia (Rapporteur) |
| R2-2102289 |
Inclusive Language Review for TS 36.306 |
Motorola Mobility (Rapporteur) |
| R2-2102295 |
Introduction of Inclusive Language |
Qualcomm (Rapporteur) |
| 10.1 |
Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
|
| R2-2101951 |
Report from session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
Vice Chairman (Nokia) |
| 10.2 |
Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
|
| R2-2101952 |
Report from Break-Out Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
Vice Chairman (ZTE) |
| 10.3 |
Session on eMTC |
|
| R2-2101953 |
Report eMTC breakout session |
Session chair (Ericsson) |
| 10.4 |
Session on NR-U, Power Savings, NTN and 2-step RACH |
|
| R2-2101954 |
Report for Rel-17 Small data and URLLC/IIoT and Rel-16 NR-U, Power Savings, and 2step RACH |
Session chair (InterDigital) |
| 10.5 |
Session on positioning and sidelink relay |
|
| R2-2101955 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 10.6 |
Session on SON/MDT |
|
| R2-2101956 |
Report from SOM/MDT session |
Session chair (CMCC) |
| 10.7 |
Session on NB-IoT |
|
| R2-2101957 |
Report NB-IoT breakout session |
Session chair (Huawei) |
| 10.8 |
Session on LTE V2X and NR V2X |
|
| R2-2101958 |
Report from session on LTE V2X and NR SL |
Session chair (Samsung) |